Trying to create a DLL from Enet source code

[slenkar]

I built the library with codeblocks,
not sure if I used debug or not,

I downloaded the archive program 7-zip and it said 7z was an unsupported format (!!!!!)
If I go off the beaten track with computers they dont work for me, for some reason.
thanks for the help so far,

I remember trying to download the ws2_32 library but I couldnt find it on google.

[stahta01]

I built the library with codeblocks,
not sure if I used debug or not,

I downloaded the archive program 7-zip and it said 7z was an unsupported format (!!!!!)
If I go off the beaten track with computers they dont work for me, for some reason.
thanks for the help so far,

I remember trying to download the ws2_32 library but I couldnt find it on google.

http://www.7-zip.org/ has 7Zip on it.
You don't need to download ws2_32 just add it to the "Link libraries" under "Linker Settings"

I will try to upload again, the 7z file seems to be damaged; I can't seem to upload Binary files right now.
ISP or http://www.savefile.com issues most likely.


I put the files on my project shown below to view them.

http://csharp-6809.svn.sourceforge.net/viewvc/csharp-6809/codeblocks/enet-1.0.7z?view=log
http://csharp-6809.svn.sourceforge.net/viewvc/csharp-6809/codeblocks/enet-1.0/

Tim S

[slenkar]

yeh I think it was damaged,

The CBP file downloaded as an XML
Ill try renaming it.

Ok I renamed it

then I put the files in the right places and double-clicked the enet.workspace
and tried to build the project but it says:

'nothing to be done'
and
if I try to run it, it says,
'needs host application'

I tried to 'rebuild' and it created a static library
libenet.a

OK I tried compiling the DLL project and added the directories and it worked, now to test if the DLL exports commands correctly!

now its acting strange, I change the Main.cpp file and press build, but it doesnt detect any errors, even when I make errors on purpose

[stahta01]

Code::Blocks does not always show errors in the build message window.
Look for then in the build log window.
I forget why this happens, I thought it was fixed till working on your issue.

Tim S