Im not sure if this has been addressed in the past (could not find a thread after a short search) but could there be a change to the #COMPILE metastatement to allow an extension to be forced.
In the examples in the PB Help...
The example #COMPILE EXE "ABC.BAS" ' Compiles to ABC.EXE seems counter-intuitive, especially applied to DLL's.
I am creating two specific types of DLL's for a project I'm working on. One set are enumerated at run time as plug-ins, the others are support DLL's used for common functions. I renamed all the plugin DLL's to PLG but you cannot compile directly to a PLG extension. It always renames to "filename.plg.dll" which I now have to go rename again.
In the examples in the PB Help...
#COMPILE EXE ' Same name as source, i.e., ABC.EXE
#COMPILE DLL ' Same name as source, i.e., ABC.DLL
#COMPILE EXE "ABC" ' Compiles to ABC.EXE
#COMPILE DLL "ABC" ' Compiles to ABC.DLL
#COMPILE EXE "ABC.BAS" ' Compiles to ABC.EXE
#COMPILE DLL ' Same name as source, i.e., ABC.DLL
#COMPILE EXE "ABC" ' Compiles to ABC.EXE
#COMPILE DLL "ABC" ' Compiles to ABC.DLL
#COMPILE EXE "ABC.BAS" ' Compiles to ABC.EXE
I am creating two specific types of DLL's for a project I'm working on. One set are enumerated at run time as plug-ins, the others are support DLL's used for common functions. I renamed all the plugin DLL's to PLG but you cannot compile directly to a PLG extension. It always renames to "filename.plg.dll" which I now have to go rename again.
Comment