There needs to be at least one ProcedureDLL for your code to be converted to a purelib, but there isn't any in your file. ProcedureDLLs get converted to PB functions. Simple procedures are just code used by those functions, and are discarded if no ProcedureDLL is found, so TailBite assumes that you're trying to build a resident file.
yep, but even with putting a ProcedureDLL (i have thousand of them in fact) in the file that includes the one i gave you, it still creates a resident file
Sorry, but the problem is still there with 1.4 (with the file i've sent you as an included file).
however now a simple ProcedureDLL in an empty file compiles the lib.
But, Polo, in that include there are only Procedures, not ProcedureDLLs, so the lib won't be compiled. What would you expect it to do? Compile a lib with no functions? Sorry, I don't understand
El_Choni wrote:But, Polo, in that include there are only Procedures, not ProcedureDLLs, so the lib won't be compiled. What would you expect it to do? Compile a lib with no functions? Sorry, I don't understand
ProcedureDLL.s Test_ReturnString() ; Trying to return a string...
Protected info.s
info.s = "Are you able to read this string when calling the command?"
ProcedureReturn info.s
EndProcedure
returns only "???????????" ^^
however, if you use the command and compile to an exe... you can read the string with an hexed in the file ^^ Btw, when using this command, 1 k will be added to the exe. Is this due fact that PB will link _SYS_InitString to the exe too?