Is there a variable (constant is better) to find out Tailbite is running?
I have a userlib which has different variables settings if it compiling with Tailbite. At the moment I have to change this value by hand... a Compilerif check will be usefull. But for this I need a constant to check if the compiler starts by Tailbite or not.
[SOLVED] Is there a variable to find out Tailbite is running
Moderators: gnozal, ABBKlaus, lexvictory
[SOLVED] Is there a variable to find out Tailbite is running
Belive! C++ version of Puzzle of Mystralia
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
Good for userlib debugging.ABBKlaus wrote:Not possible for now. Btw for what is this good for ?
Before I creating an userlib I test it as an normal Procedure for the first time and after an successful test I make the test again with the generated userlib.
Example:
Code: Select all
CompilerIf #ICEDLL = 1
ProcedureDLL ICE_GetFPS()
CompilerElse
Procedure ICE_GetFPS()
CompilerEndIf
Belive! C++ version of Puzzle of Mystralia
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
what about using the debugger directive :
Code: Select all
CompilerIf #PB_Compiler_Debugger = 1
MessageRequester("INFO","Now in debug mode")
CompilerElse
MessageRequester("INFO","Normal mode")
CompilerEndIf
Sorry, but this is not what I mean.ABBKlaus wrote:what about using the debugger directive :
I have an own test environment which is running in realease mode of the userlib. But It is different between calling as Procedure and ProcedureDLL.
Belive! C++ version of Puzzle of Mystralia
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
-
- Addict
- Posts: 2345
- Joined: Mon Jun 02, 2003 9:16 am
- Location: Germany
- Contact:
Btw.: You can use ProcedureDLL without creating a dll/userlib and run it like normal applicationsIceSoft wrote:Sorry, but this is not what I mean.ABBKlaus wrote:what about using the debugger directive :
I have an own test environment which is running in realease mode of the userlib. But It is different between calling as Procedure and ProcedureDLL.

Code: Select all
ProcedureDLL Test()
MessageRequester("Hello", "ProcedureDLL or Procedure?")
EndProcedure
Test()
Last edited by DarkDragon on Thu May 29, 2008 11:42 am, edited 1 time in total.
bye,
Daniel
Daniel
Is this an official PureBasic feature? If yes I will use it.DarkDragon wrote:Btw.: You can use ProcedureDLL without creating a dll/userlib and run it like normal applications.
Belive! C++ version of Puzzle of Mystralia
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
Bug Planet
<Wrapper>4PB, PB<game>, =QONK=, PetriDish, Movie2Image, PictureManager,...
-
- Addict
- Posts: 2345
- Joined: Mon Jun 02, 2003 9:16 am
- Location: Germany
- Contact:
Well you can expect that it will run in all future versions, because in the assembler source you'll just see another label like a normal procedure and an export in the export table, but as you don't create a DLL you don't have an export table. As long as you don't use ProcedureCDLL it should work fine.IceSoft wrote:Is this an official PureBasic feature? If yes I will use it.DarkDragon wrote:Btw.: You can use ProcedureDLL without creating a dll/userlib and run it like normal applications.
bye,
Daniel
Daniel