News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Codeblocks does not create DLL file.

Started by rnodal, May 30, 2008, 08:37:45 PM

Previous topic - Next topic

rnodal

Hello all:

I recently decided to go from Linux to Windows to pretty much check the performance of my library across both operating system. The problem is that I'm trying to create a dll out of my library in windows and while it compiles and built I can't find the dll file even though Codeblocks tells me it has created one. All I find is the a file but that's it. What could be causing this. Code problems or Codeblocks mis-configured? Any input would be appreciated. Thanks!


-r

Jenna

I guess it's a misconfiguration.

You can build a sample dll with the wizard and look at the code ,the Build options and the Projects properties to see what settings are needed to build a dll.

rnodal

I just noticed that it is giving me some sort of error.

Cannot export SDL_image_NULL_THUNK_DATA: symbol not found


Is this error supposed to stop the building of a dll process?



-r

rnodal

I found the problem.

My macro to determine to export or to import was spelled correctly.  :oops:

Thanks all.

rnodal

Quick question. How do I place *.a files somewhere else different from *.dll files?


Thanks.

Deschamps

Quote from: rnodal on May 30, 2008, 09:31:56 PM
Quick question. How do I place *.a files somewhere else different from *.dll files?

If I've understood your question, you should have defined different build targets (building static or shared libraries), so you can specify different places for the build in each one. But this seems to me a trivial matter, so maybe it's my misunderstanding of your question :)

Regards.
Those who were seen dancing were thought to be insane by those who could not hear the music

rnodal

It is not important any more but what I meant was how can I separate the import library created by CB *.a file from the *.dll file. CB places the *.a files under the same folder as the *.dll file. Thanks anyways. Take care.

-r

DevLord

I have the same problem  :( but i do not know how to resolve it, can you explain who it works ?