User forums > General (but related to Code::Blocks)
Enet and CodeBlocks
oster:
EDIT
well i did the ./configure && make && make install
But how did that help me it just made two folders that i can see .deps and .libs and tossed in some random files. i dont know how to use it still. Do i add the include folder to the project and .libs folder it made?
georger:
--- Quote from: oster on August 11, 2013, 09:49:37 pm ---EDIT
well i did the ./configure && make && make install
But how did that help me it just made two folders that i can see .deps and .libs and tossed in some random files. i dont know how to use it still. Do i add the include folder to the project and .libs folder it made?
--- End quote ---
Your question is not really C::B related. That said, I'll help.
I just downloaded the ENet source distribution (enet-1.3.8.tar.gz) and uncompressed it to a temp folder.
Surprise, there's an enet_dll.cbp C::B project file in it! Let's open it in C::B... Ok, it opened.
Build target is Debug. Let's click Build (Ctrl-F9)... 3 seconds later, I have 3 shiny new files in bin\Debug: libenet.a, libenet.def, and libenet.dll.
Now let's change the target to Release and click Build again... 3 seconds later, let's look at bin\Release, our files are there.
There you have it, static and dynamic libraries ready for linking.
By the way, now you're on your own. I'm still trying to figure out why the mods didn't remove this thread yet...
oster:
--- Quote from: georger on August 12, 2013, 11:06:15 pm ---
--- Quote from: oster on August 11, 2013, 09:49:37 pm ---EDIT
well i did the ./configure && make && make install
But how did that help me it just made two folders that i can see .deps and .libs and tossed in some random files. i dont know how to use it still. Do i add the include folder to the project and .libs folder it made?
--- End quote ---
Your question is not really C::B related. That said, I'll help.
I just downloaded the ENet source distribution (enet-1.3.8.tar.gz) and uncompressed it to a temp folder.
Surprise, there's an enet_dll.cbp C::B project file in it! Let's open it in C::B... Ok, it opened.
Build target is Debug. Let's click Build (Ctrl-F9)... 3 seconds later, I have 3 shiny new files in bin\Debug: libenet.a, libenet.def, and libenet.dll.
Now let's change the target to Release and click Build again... 3 seconds later, let's look at bin\Release, our files are there.
There you have it, static and dynamic libraries ready for linking.
By the way, now you're on your own. I'm still trying to figure out why the mods didn't remove this thread yet...
--- End quote ---
Yes that worked thank you for your time and help. Next time when i have a problem like this i will not post here. But if i do have another question like this is there a good forum maybe on a different site that code help me that use codeblocks?
georger:
--- Quote from: oster on August 13, 2013, 08:55:33 pm ---Yes that worked thank you for your time and help. Next time when i have a problem like this i will not post here. But if i do have another question like this is there a good forum maybe on a different site that code help me that use codeblocks?
--- End quote ---
I don't know of any such forum or site.
C++ has a steep learning curve both as a language AND as an ecosystem. If you're really interested in C++, sooner or later you'll have to learn about compiling, linking, makefiles, and configure scripts. Also about tools like CMake and premake. Take a look at chapter 2 of this book for a introduction to the subject.
Next time you have such a question, try to find an answer by yourself - no offense.
Play around with the build options of your project:
- Add the correct libraries in "Linker settings". You'll want to put common link libraries in the root target, and specific the appropriate libraries in the Debug and Release targets;
- Add the appropriate include and lib directories in the "Compiler" and "Linker" tabs in "Search directories".
Your problem is not a C::B problem. C::B offers a simple and powerful interface for organizing, compiling and linking your project, but you are responsible for setting it up.
Once again, you're on your own.
oster:
--- Quote from: georger on August 13, 2013, 10:25:47 pm ---
C++ has a steep learning curve both as a language AND as an ecosystem. If you're really interested in C++, sooner or later you'll have to learn about compiling, linking, makefiles, and configure scripts. Also about tools like CMake and premake. Take a look at chapter 2 of this book for a introduction to the subject.
--- End quote ---
Yes i have been using c++ for 5 years and using Visual Studio 2008 express i had to never compile or recompile a library from source i had to just link to the .lib file and include folders so that was my problem, linking i have worked plenty with make files i have never touched CMake and premake heard of but never used. I will take a look at that link you shared also.
--- Quote from: georger on August 13, 2013, 10:25:47 pm ---Next time you have such a question, try to find an answer by yourself - no offense.
--- End quote ---
Non taking since i did and the only thing i found relevant was the link i shared in my first post
Thanks for your help even though i posted a non related c::b question.
Navigation
[0] Message Index
[*] Previous page
Go to full version