Changing the target filename in program/options doesnt seem to recognise anything after a fullstop (eg TestModule.xxx) - is there any way to override this ? (other than manually renaming after a compile)

Thanks

A test.lpr file should be compiled to a test.nlx file. Something like this:

ppc386 -otest.nlx test.lpr

Mattias

Changing the target filename in program/options doesnt seem to recognise anything after a fullstop (eg TestModule.xxx) - is there any way to override this ? (other than manually renaming after a compile)

What do you mean with fullstop?

I just tried and it seems to work: Setting the target filename changes the output file of the compilation.

Mattias

If my application Title is 'Test' and I change the target filename to 'Test.nlx' it only compiles as 'Test' - ignores anything after the period (fullstop) - am I using this incorrectly ?

I didn't know, that fpc is doing this. Under win32 it makes sense to change the file extension, but under linux?
I hope, someone of the fpc-team is reading this and can explain.

Underscore works. Can you use Test_nlx instead?

Mattias

I can't reproduce it with the compiler (test with 1.0.6). I created a test.lnx.pas and it compiled into test.lnx and under win32 i created a test.win32.pas and it compiled to test.win32.exe

Peter

If my application Title is 'Test' and I change the target filename to 'Test.nlx' it only compiles as 'Test' - ignores anything after the period (fullstop) - am I using this incorrectly ?

Underscore solves my prob - I use this when loading modules for my program to differentiate development/completed. Once a module is complete, all I have to change is the target filename Thanks