Revision history for ProPgPrebuiltLibraries


Revision [22020]

Last edited on 2017-11-21 01:12:02 by JeffMarshall [fix page link name case]
Additions:
- The static library must be linked at compile time by using either ##[[KeyPgInclib|#inclib]]## in the source code or by using the ##[[CompilerOptl|-l]]## option on the command line to specify the name of the library.
Deletions:
- The static library must be linked at compile time by using either ##[[KeyPgInclib|#inclib]]## in the source code or by using the ##[[CompilerOptL|-l]]## option on the command line to specify the name of the library.


Revision [21982]

Edited on 2017-11-16 08:56:11 by St_W [add note on library architecture requirement]
Additions:
Note that the system architecture of the library has to match the architecture of the application. For example, to successfully use a library in a x86 (32-bit) application, a x86 (32-bit) library is required.


Revision [21980]

Edited on 2017-11-16 08:47:20 by St_W [add links to static/shared libs descriptions; refer to extLibTOC]
Additions:
See the [[ExtLibTOC|External Libraries Index]] for an overview of the additional headers shipped with ""FreeBASIC"". The page also describes the file(s) that need to be included to use the library. Alternatively one can browse the "inc/" directory located where ""FreeBASIC"" was installed to find other headers. It is possible that headers might be available for a library you need to use. Some headers are located in "inc/" and others might be located in a sub-directory. To include headers located in a subdirectory of "inc/", prefix the name of the header with the name of the directory where it is located. For example:
- The static library must be linked at compile time by using either ##[[KeyPgInclib|#inclib]]## in the source code or by using the ##[[CompilerOptL|-l]]## option on the command line to specify the name of the library.
{{fbdoc item="see"}}
- [[ProPgStaticLibraries|Static Libraries]]
- [[ProPgSharedLibraries|Shared Libraries (DLLs)]]
Deletions:
Browse the "inc/" directory located where ""FreeBASIC"" was installed to find other headers. It is possible that headers might be available for a library you need to use. Some headers are located in "inc/" and others might be located in a sub-directory. To include headers located in a subdirectory of "inc/", prefix the name of the header with the name of the directory where it is located. For example:
- The static library must be linked at compile time by using either ##[[KeyPgInclib|#inclib]]## in the source code or by using the //-l// option on the command line to specify the name of the library.


Revision [20651]

Edited on 2016-02-10 16:13:11 by DkLwikki [Update link format]
Additions:
- ##datetime.bi## - Declarations for ##[[KeyPgDateSerial|DateSerial]]##, ##[[KeyPgDateValue|DateValue]]##, ##[[KeyPgIsDate|IsDate]]##, ##[[KeyPgYear|Year]]##, ##[[KeyPgMonth|Month]]##, ##[[KeyPgDay|Day]]##, ##[[KeyPgWeekday|Weekday]]##, ##[[KeyPgTimeserial|TimeSerial]]##, ##[[KeyPgTimeValue|TimeValue]]##, ##[[KeyPgHour|Hour]]##, ##[[KeyPgMinute|Minute]]##, ##[[KeyPgSecond|Second]]##, ##[[KeyPgNow|Now]]##, ##[[KeyPgDateAdd|DateAdd]]##, ##[[KeyPgDatePart|DatePart]]##, ##[[KeyPgDateDiff|DateDiff]]##, ##[[KeyPgMonthname|MonthName]]##, ##[[KeyPgWeekdayname|WeekdayName]]##
- ##dir.bi## - Constants to be used with ##[[KeyPgDir|Dir]]##
- ##fbgfx.bi## - Additional constants and structures to be used with graphics commands such as ##[[KeyPgMultikey|Multikey]]##, ##[[KeyPgScreencontrol|Screencontrol]]##, and ##[[KeyPgScreenevent|Screenevent]]##, ##[[KeyPgImagecreate|Imagecreate]]##.
- ##file.bi## - Declarations for ##[[KeyPgFilecopy|FileCopy]]##, ##[[KeyPgFileattr|FileAttr]]##, ##[[KeyPgFilelen|FileLen]]##, ##[[KeyPgFileexists|Fileexists]]##, ##[[KeyPgFiledatetime|FileDateTime]]##
- ##string.bi## - Declarations for ##[[KeyPgFormat|format]]##
- The source code must include the appropriate headers using ##[[KeyPgInclude|#include]]##.
- The static library must be linked at compile time by using either ##[[KeyPgInclib|#inclib]]## in the source code or by using the //-l// option on the command line to specify the name of the library.
- The source code must include the appropriate headers using ##[[KeyPgInclude|#include]]##.
Deletions:
- ##datetime.bi## - Declarations for ##[[KeyPgDateSerial DateSerial]]##, ##[[KeyPgDateValue DateValue]]##, ##[[KeyPgIsDate IsDate]]##, ##[[KeyPgYear Year]]##, ##[[KeyPgMonth Month]]##, ##[[KeyPgDay Day]]##, ##[[KeyPgWeekday Weekday]]##, ##[[KeyPgTimeserial TimeSerial]]##, ##[[KeyPgTimeValue TimeValue]]##, ##[[KeyPgHour Hour]]##, ##[[KeyPgMinute Minute]]##, ##[[KeyPgSecond Second]]##, ##[[KeyPgNow Now]]##, ##[[KeyPgDateAdd DateAdd]]##, ##[[KeyPgDatePart DatePart]]##, ##[[KeyPgDateDiff DateDiff]]##, ##[[KeyPgMonthname MonthName]]##, ##[[KeyPgWeekdayname WeekdayName]]##
- ##dir.bi## - Constants to be used with ##[[KeyPgDir Dir]]##
- ##fbgfx.bi## - Additional constants and structures to be used with graphics commands such as ##[[KeyPgMultikey Multikey]]##, ##[[KeyPgScreencontrol Screencontrol]]##, and ##[[KeyPgScreenevent Screenevent]]##, ##[[KeyPgImagecreate Imagecreate]]##.
- ##file.bi## - Declarations for ##[[KeyPgFilecopy FileCopy]]##, ##[[KeyPgFileattr FileAttr]]##, ##[[KeyPgFilelen FileLen]]##, ##[[KeyPgFileexists Fileexists]]##, ##[[KeyPgFiledatetime FileDateTime]]##
- ##string.bi## - Declarations for ##[[KeyPgFormat format]]##
- The source code must include the appropriate headers using ##[[KeyPgInclude #include]]##.
- The static library must be linked at compile time by using either ##[[KeyPgInclib #inclib]]## in the source code or by using the //-l// option on the command line to specify the name of the library.
- The source code must include the appropriate headers using ##[[KeyPgInclude #include]]##.


Revision [15731]

Edited on 2012-01-18 07:53:42 by DkLwikki [CamelCase links]
Additions:
""FreeBASIC"" is distributed with many headers for common or popular libraries. The headers allow a programmer to use functions available in these existing static or shared libraries (DLLs).
The libraries themselves are not distributed with ""FreeBASIC"", but most can be downloaded from the web and readily installed. Some other libraries may need to be first compiled from sources to be used. Please see the documentation for the specific library on how to configure, install, and use them.
Some static or shared libraries (DLLs) may be already present on the system since they might be part of ""FreeBASIC"" itself or the operating system.
Although many headers can be used on any of the platforms supported by ""FreeBASIC"", some headers are platform specific and will not be usable on other platforms.
There are a few headers that are specific to ""FreeBASIC"" and expose some functions that are otherwise not available:
Many (many) headers for the Windows API are available for inclusion in ""FreeBASIC"" source code. In most cases the only include file needed is "windows.bi". For example,
Browse the "inc/win/" directory where ""FreeBASIC"" was installed to see all of the available Windows API headers.
Browse the "inc/" directory located where ""FreeBASIC"" was installed to find other headers. It is possible that headers might be available for a library you need to use. Some headers are located in "inc/" and others might be located in a sub-directory. To include headers located in a subdirectory of "inc/", prefix the name of the header with the name of the directory where it is located. For example:
'' located at inc/curl.bi
'' located at inc/GL/gl.bi
Deletions:
FreeBASIC is distributed with many headers for common or popular libraries. The headers allow a programmer to use functions available in these existing static or shared libraries (DLLs).
The libraries themselves are not distributed with FreeBASIC, but most can be downloaded from the web and readily installed. Some other libraries may need to be first compiled from sources to be used. Please see the documentation for the specific library on how to configure, install, and use them.
Some static or shared libraries (DLLs) may be already present on the system since they might be part of FreeBASIC itself or the operating system.
Although many headers can be used on any of the platforms supported by FreeBASIC, some headers are platform specific and will not be usable on other platforms.
There are a few headers that are specific to FreeBASIC and expose some functions that are otherwise not available:
Many (many) headers for the Windows API are available for inclusion in FreeBASIC source code. In most cases the only include file needed is "windows.bi". For example,
Browse the "./inc/win/" directory where FreeBASIC was installed to see all of the available Windows API headers.
Browse the "./inc/" directory located where FreeBASIC was installed to find other headers. It is possible that headers might be available for a library you need to use. Some headers are located in "./inc/" and others might be located in a sub-directory. To include headers located in a subdirectory of "./inc/", prefix the name of the header with the name of the directory where it is located. For example:
'' located in ./inc/
'' located in ./inc/GL


Revision [14802]

Edited on 2010-08-21 13:07:49 by GaLeon [Changed run-time to runtime]
Additions:
{{fbdoc item="section" value="C Runtime (CRT)"}}
Where possible cross-platform compatible headers have been provided for the C runtime (CRT). For example,
Deletions:
{{fbdoc item="section" value="C Run-Time (CRT)"}}
Where possible cross-platform compatible headers have been provided for the C run-time (CRT). For example,


Revision [12016]

The oldest known version of this page was created on 2008-01-03 15:26:34 by ElSairon [Changed run-time to runtime]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki



sf.net phatcode