Page 1 of 1

CodeLite architecture (static vs dyn libs)

Posted: Fri Sep 03, 2010 2:04 pm
by jfouche
Hi Eran

I'm currious ;)
I would like to know if there is a technical reason why you use static libs for codelite, wxsqlite, wxscintilla, ... instead of dynamic libs.
I think (but without a full comprehension of this product, I may be wrong), that using dynamic libs for those components should speed the compilation time (which is awfull long for my old computer : about 1H30 for a clean build), and make the plugins size smaller (as binary code will not be duplicated).
Thanks for your time to answer me

Re: CodeLite architecture (static vs dyn libs)

Posted: Fri Sep 03, 2010 6:10 pm
by eranif
No reason, except the historical one - I might change it to shared libraries but I dont see it as a top priority task.
FYI: Under Linux/Mac all the mentioned libraries are built as shared objects

Eran

Re: CodeLite architecture (static vs dyn libs)

Posted: Mon Oct 18, 2010 1:51 pm
by eranif
Hi again,

I changed codelite architecture to use DLL under Windows as well (there were quite few bugs on the way especially with regards to singletons)
I will commit the changes soon and will update this post when its done

EDIT: code committed
Eran

Re: CodeLite architecture (static vs dyn libs)

Posted: Mon Oct 18, 2010 7:29 pm
by jfouche
Thanks a lot.
I'll try an update this evening, and see if it's better for me.