Page 1 of 1

Frameworks as opposed to Libraries under OSX

Posted: Mon May 28, 2018 9:06 am
by sausage
Hi Guys,

I help out with the Orx Portable Game Engine project, which supports multiple OSes and IDEs. A Codelite build is provided for all OSes.

We have noticed a problem with Codelite not supporting the -framework switch for MacOSX frameworks.

Our Codelite project has these options, for example:

Code: Select all

LinkOptions            :=  -dynamiclib -m32 -L/usr/lib32 -dead_strip 
Libs                   := $(LibrarySwitch)webpdecoder $(LibrarySwitch)liquidfun $(LibrarySwitch)Foundation.framework
In this example, there are some linker options, and the Libs contains both a mixture of Libraries and Frameworks.

Compiling the project will give a linker error:

Code: Select all

ld: library not found for -lFoundation.framework
Which is correct because there is no such library, but rather a framework.

Codelite can be made to work by bypassing it’s options, and feeding handwritten parameters to the compiler directly (using the linker options) with:

Code: Select all

LinkOptions            :=  -framework Foundation
..and removing the Foundation.framework from the specified Libs.

Is this possible in any way to get framework support in Codelite, or could it be supported in a future version?

Re: Frameworks as opposed to Libraries under OSX

Posted: Tue May 29, 2018 11:37 pm
by eranif
Please submit a feature request

Thanks

Re: Frameworks as opposed to Libraries under OSX

Posted: Wed May 30, 2018 9:02 am
by sausage
Will do, thanks eranif.

Re: Frameworks as opposed to Libraries under OSX

Posted: Wed May 30, 2018 9:27 am
by sausage