U++ framework
Do not panic. Ask here before giving up.

Home » Developing U++ » U++ Developers corner » Linking standard libraries
Re: Linking standard libraries [message #35298 is a reply to message #35297] Mon, 30 January 2012 10:21 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14290
Registered: November 2005
Ultimate Member
dolik.rce wrote on Mon, 30 January 2012 03:06

mirek wrote on Mon, 30 January 2012 08:45

I guess nothing else than to reduce number of required prerequisites to run U++. In theory, embedding the code covers more platforms than not to.

But I agree that we perhaps should 'move' some libraries to png-like state.


I wonder if there is some way to figure out if there is given library present at compile time? So that we could switch between the outer linking and embedded code as necessary... OTOH, this would probably lead to having such code in TheIDE and stronger dependency of U++ on this particular IDE, which is not a good thing.

So what about adding a flag into each of these libraries, something like EMBED_JPG? It would be always on for win32 and on other platforms, developer can use it only when he needs it (e.g. when he knows he will ship his app to system where libjpeg is missing)?

Honza


I guess let us just move them... In the end, we already depend on some shared libraries that are in fact less likely to be present (e.g. gtk), so moving bz2 etc is not a big issue IMO.

That said, do we have some list of libs to move?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: U++ and MinGW 4.7 (-std=c++11) issues
Next Topic: Install script for Ubuntu
Goto Forum:
  


Current Time: Wed Apr 29 09:27:35 GMT+2 2026

Total time taken to generate the page: 0.00599 seconds