Feature for the pbeditor
Can the "Executable Location" that is saved be unique per type of compiler, to make it easier for multi-platform / multi-architecture compiling using the same source file. (I have a product at the moment that requires me to do 32 and 64 bit windows builds and I occasionally overwrite the wrong file)
So, instead of Executables=yourname.exe at the end of the pb file,
something like:
exewin32=win32bit\yourname.exe
exewin64=win64bit\yourname.exe
exelin32=lin32\yourname
exelin64=lin64\yourname
exemac32=mac32\yourname
exemac32=mac64\yourname
exeamiga=amiga\yourname.bin
Compiler executable name
Re: Compiler executable name
I do this with a batch file.
The exe and other files are moved or copied to a separate directory after compilation.
You can pass parameters to the batch file, for example: %EXECUTABLE %PROJECT 64
With this you can use the parameters in the batch file with %1 %2 %3.
Peter
The exe and other files are moved or copied to a separate directory after compilation.
You can pass parameters to the batch file, for example: %EXECUTABLE %PROJECT 64
With this you can use the parameters in the batch file with %1 %2 %3.
Peter
Re: Compiler executable name
Have you already tried a project? Making a difference between 32 and 64 bit shouldn't be a problem. If you can also make differences between Win/Linux/Mac, I don't know, because I only use Windows.
sorry for my bad english