the Community Command pack - "Emergence Basic Edition"
Converted to run with EBasic :-) the idea to create a Community based command pack, keeping it open source,
allowing anyone to add/improve/fix commands...
the IBP verion did`t live that long & only had one command added :-) maybe it will do better here :-) if not, then
it is a example on how to create a command pack :-)
the attachment contains all source & helpfiles, now if anyone add`s commands to the pack if you send me the
updated pack i will update the attachement on this post, just to keep it all in one place :-)
_________________________________________________________________________________________
The Archive has been updated to include the additional command from http://www.ionicwind.com/forums/index.php/topic,1661.0.html - (0019)
Last updated 02-067-07 (see above topic for more info)
ccFindAndReplace removed as ccFandR has been added by flicko.
ntddl.lib - you will have to add this using create import library
How did you create the .lib file in EBasic? I have 1.5 with only options are "Window", "Console" "DLL" for output/target options.
Hi Sync,
start a new project, insert your files and from the Project option menu choose "Static Library" in the project type combo box.
byeÂÃ, :-X
Sergio
Yep. A single file static library is kind of redundant. You can just take the single .o file and rename it .lib ;)
Heh, thats interesting :) Would be super cool if that was listed in the manual? I probably missed it though :( Anyways, thanks for the tips and tricks guys.
Quote from: Paul Turley on December 07, 2006, 05:08:39 AM
Yep. A single file static library is kind of redundant. You can just take the single .o file and rename it .lib ;)
didnt know that, thank for pointing out Paul :)
You can also use a single .o (object) file directly in a project by selecting the 'Project' menu and chosing 'Insert library/object into project'. Which adds that file to the list of files the linker builds with.
I use this method to include raw assembler created object files in my projects. It is also an alternative to using the $use statement, since you can add import libraries to the build without having to put them in the .libs directory.
A lot of flexebility there ;)