Posted: Thu Apr 10, 2003 9:26 pm
Restored from previous forum. Originally posted by tinman.
If anyone is developing a PB library for Windows in C they might be interested in http://www.bloodshed.net. It is a free (GPL) compiler and IDE based on GCC. IMO it has a better interface and project management than LCC. It seems to work very nicely at creating PB libraries.
Tip: If you choose to create a "Win32 static library" from the project templates then you will get a "libfile.a" style library. However, this is already in the correct format, you just need to rename it to libfile.lib to get it to work with LibraryMaker.
You can also automate this process by creating a file called something like pb_lib.mak and including the following in it:
It should also be possible to run library maker automatically but I have not had any success with that.
Because the compiler is GCC 3.2 it should be possible to write code which compiles on multiple platforms. Of course, using OS specific functions or features reduces the usefulness of that, but it is still there
--
I used to be a nihilist but I don't believe in that any more.
(Win98first ed. + all updates, PB3.51, external editor)
If anyone is developing a PB library for Windows in C they might be interested in http://www.bloodshed.net. It is a free (GPL) compiler and IDE based on GCC. IMO it has a better interface and project management than LCC. It seems to work very nicely at creating PB libraries.
Tip: If you choose to create a "Win32 static library" from the project templates then you will get a "libfile.a" style library. However, this is already in the correct format, you just need to rename it to libfile.lib to get it to work with LibraryMaker.
You can also automate this process by creating a file called something like pb_lib.mak and including the following in it:
Code: Select all
# Change this to whatever path you have PureBasic installed in
LIBMAKER = "D:\Program Files\PureBasic\Library SDK\LibraryMaker.exe"
# Note the indents here must be tabs I think
all-after:
rm -f $(basename $(BIN)).lib
mv $(BIN) $(basename $(BIN)).lib
Because the compiler is GCC 3.2 it should be possible to write code which compiles on multiple platforms. Of course, using OS specific functions or features reduces the usefulness of that, but it is still there
--
I used to be a nihilist but I don't believe in that any more.
(Win98first ed. + all updates, PB3.51, external editor)