If I run some console code and I have an rc file mentioned in WinFBE's 'Additional compiler switches (optional):' then the compilation will fail. On the other hand, having removed the rc file, I may then run some code which needs it and the compilation fails again. One solution to this is to add to the 'Build Configurations...'. That saves me either deleting or adding. However, I will still get a failed compilation if I forget to choose the correct build for the current code. With WinFBE the default build is Win32 Console (Release) on opening.
With poseidonFB we have in the ini file [customCompilerOptions] the first entry being 'current=<Whatever>' where <Whatever> is the last build we used. This is better because I may be working on the same code for a few days and find the correct build on opening. However, if I write some test snippet then I may need a different build for that and I could fall foul with that.
What I would really like is a build association. Load xyz.bas and the associated build is chosen for us. With a new bas then an associated build could be saved on the first compilation. This will not be an easy task for either WinFBE or poseidonFB.
Along comes JK-IDE which does not have any fancy build lists and dialogs to negotiate. What we have is '#Compile'.
For example:
Code: Select all
#Compile exe console 32 /o "-gen gcc -Wc -O3 AES-RSA-ECDSA.rc"
I have an application which I wrote some years ago which runs from the StartUp folder. It uses switches but they are not put into a command line but in an ini file. There are six possible switches and the current ini file is '/silent /displayonce /schedule: 180. It does some 'crunching' every 180 minutes, runs silently except on a Restart/Boot when is displays a TaskDialog. The other three switches are development related and not used in release code.
Both WinFBE and poseidonFB could look for an ini file separate to their current ini files which has nothing in it except switches and could be given precedent over any other builds mentioned in the IDEs. Association? Easy. We simply put a build ini file in the same directory as the bas. Chances are that I would cease to use either WinFBE's or poseidonFB's build systems and make sure every bas has a build ini. I have a folder for experimental code and test snippets. I could have a simple default build ini put there.
Any thoughts?