{$IFDEF LAZ_VERSION} ?

[BigChimp]

CPU64 etc predefined symbols are there.

[Fred vS]

CPU64 etc predefined symbols are there.

Ok, i did a search for predefined symbols but did not find any complete list of  predefined symbols used by fpc.

Ok bis => I stop, i was not able to explain what i wanted, i loose.

By the way, thanks to try to help me.

Fre;D.

[BigChimp]

Riiiiight.... don't know what you searched...

http://www.freepascal.org/docs-html/prog/progsu127.html#x137-1380002.1.1
links to
http://www.freepascal.org/docs-html/prog/progap7.html#x333-348000G

Have fun.

PS: By the way, if you search for CPU64 in the wiki search box, the second hit is this:
http://wiki.lazarus.freepascal.org/Platform_defines

[Zoran]

In LCL, there are widgetset defines. See:
http://wiki.freepascal.org/Code_Conversion_Guide#Useful_compiler_variables_.2F_defines_.2F_macros

[Fred vS]

Riiiiight....

=> 

http://www.freepascal.org/docs-html/prog/progsu127.html#x137-1380002.1.1
links to
http://www.freepascal.org/docs-html/prog/progap7.html#x333-348000G

Hum, much better (but not perfect => the list is not complete => random example => "ifdef library" is missing.)

PS: By the way, if you search for CPU64 in the wiki search box, the second hit is this:

CPU64 was a example, to try to explain what i want...

In LCL, there are widgetset defines. See:
http://wiki.freepascal.org/Code_Conversion_Guide#Useful_compiler_variables_.2F_defines_.2F_macros

Yep, nice one, it is something like this that i am looking for  (but more exhaustive...)

Thanks.

[BigChimp]

CPU64 was a example, to try to explain what i want...

Yes, and your point is? Does this mean you cannot use it as a search term?

[marcov]

Riiiiight....

=> 

http://www.freepascal.org/docs-html/prog/progsu127.html#x137-1380002.1.1
links to
http://www.freepascal.org/docs-html/prog/progap7.html#x333-348000G

Hum, much better (but not perfect => the list is not complete => random example => "ifdef library" is missing.)

When does FPC define "Library" ?

I tested with compiling a dll, and it doesn't seem to define that. Are you sure you are not confused with some third party define?

[Fred vS]

I tested with compiling a dll, and it doesn't seem to define that. Are you sure you are not confused with some third party define?

Hum, let me show a example that is working for me.

It is used by the uos project. => That project let you use uos.pas as "traditional" unit, usable for fpc developers, for their programs.

But a other part of the project is to create a library.

In the main uos.pas unit, there are some :

Code: [Select]

{$IF DEFINED(Library)}
...// do something..
     {$else}
..// do other thing...
     {$endif}
=> So the compiler knows if the main project is a "traditional" program or a library.

And i would have (sorry, im a big curious) a list of all the symbols used by fpc ( => to avoid to use a  {$DEFINE something}  already pre-defined by fpc or Lazarus...

Fre;D

[Fred vS]

When does FPC define "Library" ?

Ooooops, Marcov, i apologize  , indeed  "Library" is not yet define by fpc, it is me who defined it in top of uos.pas unit (and user has to uncomment it manually if he want a library).

So you see, one more reason to have a complete list of pre-defined things... 

Fre;D

[marcov]

So you see, one more reason to have a complete list of pre-defined things... 

I still have not seen any indication that the manual isn't. Of course there are undocumented defines, but they are not documented on purpose (and usually start with FPC_*)

Even if there are one or two missing,  I don't see the point to start a new documentation initiative.