Search found 37 matches
Re: Compiling
I guess the term 'noob' is so broad that it needs to be defined in order for everyone to be on the same page. They expect things to be handed to them on a silver platter, without having to put in any effort themselves. I actually would love to hand things to people on a silver platter. Which is why ...
- Wed Mar 24, 2010 22:03
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
Hmm. Some of the problem will also be that when you link statically, it will only bring in .o files from the archives that contain stuff you directly reference - so most of the CEGUI stuff is going to be discarded Really? I wasn't aware of that. So there is no way to tell it to bring it all in no m...
- Wed Mar 24, 2010 20:31
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
So I found the below code, but I'm thinking I can't have it both ways here. Because I want to statically link CEGUI to my DLL, but also want the CEGUI classes/methods exposed through my DLL as well. Yet you can't get the dllexport when static is defined. So if this is what I want is my only option t...
- Wed Mar 24, 2010 14:52
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
OK, so that worked. I can now use my class and it's methods. But when I try to put CEGUI specific code into the exe program I get linker errors about the missing functions. My assumption is that since I statically linked the CEGUI stuff into my own DLL, that my DLL's lib file would have these in the...
Re: Compiling
Crazy Eddie you are the best! I was very shocked at how much you do help. You post pretty much every day and I think that's amazing and I fully do appreciate you. I know the support role can grind a person down (I do this at work all the time even though I'm a developer) but you are truly good at it...
- Wed Mar 24, 2010 12:11
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
I actually did that, but now that I think about it, always best to sleep on an issue
, I didn't do that on the constructor/destructor functions. I'm guessing that's it! I didn't use a macro for the export/import I just typed it out ![Smile :)](./images/smilies/icon_smile.gif)
![Smile :)](./images/smilies/icon_smile.gif)
![Smile :)](./images/smilies/icon_smile.gif)
- Wed Mar 24, 2010 01:54
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
So maybe I'm thinking about this the wrong way. I don't have much experience with making dlls/libraries in C++. My plan was to compile statically CEGUI into my own custom dll. So I created this custom dll project, and statically linked the parts of CEGUI I need. That worked all fine. I got a dll and...
- Wed Mar 24, 2010 00:28
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
Cool, I got this working in an exe. So my next steps will be to make my own dll and statically link all these dependencies into it, and then all the users of this engine should need is the includes, my lib, and the dll and it should be good to go! They will be excited for sure. Thanks for your help ...
Re: Compiling
those who will probably contribute more to the project than noobs ever will See generally I think the reason you make a library is so people can use it, not so people will contribute to it. So those noobs are really your target audience when you make a library. Isn't the idea to make something that...
Re: Compiling
I think the ideal thing, but a lot of work, would be to include all source and then have some sort of GUI configuration program that let's you graphically configure what you want and then builds everything for you. I imagine the building can all be done from command line.
- Mon Mar 22, 2010 18:36
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
Oh I see. If I change my project to /MT then all msvcprt.lib errors go away and all that is left are: 1>CEGUIBase_Static.lib(CEGUISystem.obj) : error LNK2001: unresolved external symbol __imp__timeGetTime@0 1>CEGUIBase_Static.lib(CEGUIFreeTypeFont.obj) : error LNK2001: unresolved external symbol _FT...
- Mon Mar 22, 2010 18:19
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
Of course if you change your projects msvc runtime configuration to /MT and link to the new precompiled static libraries, you can avoid having to build all of the dependencies from source...in theory (I haven't actually tested the new packages myself). I guess I thought that's what I was doing. hmm
- Mon Mar 22, 2010 15:02
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
So since premake wasn't working for me I just created an empty static library project. I added all the .cpp files and added the .h directory. I then added the jpeg, png, & zlib libraries. I have 1 error and not sure what to do about it. Error 42 error C2491: 'SILLY::ImageLoaderManager::d_instanc...
- Mon Mar 22, 2010 11:42
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
SILLY uses premake for MSVC++ solution creation, so just run the premake.exe (you can use the one from CEGUI) in the root SILLY directory - as an aside, does the source package not contain the solution? hmm, I did run the premake that was in the SILLY dir but it didn't work. It just closes really f...
- Sun Mar 21, 2010 17:59
- Forum: Help
- Topic: static linking issues
- Replies: 19
- Views: 11414
Re: static linking issues
Is there a VS setup for SILLY? I see this has some dependencies of some jpeg/png lib? This rabit hole is deep ![Smile :)](./images/smilies/icon_smile.gif)
![Smile :)](./images/smilies/icon_smile.gif)