URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=12575>
Summary: suggestion about header files in frameworks
Project: GNUstep
Submitted by: wolfgang
Submitted on: mer 06.04.2005 � 03:04
Category: Makefiles
Severity: 3 - Normal
Item Group: Change Request
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
_______________________________________________________
Details:
The current filesystem infrastucture for frameworks is a follows:
[name].framework/Headers -> Versions/Current/Headers
[name].framework/Resources -> Versions/Current/Resources
[name].framework/Versions
[name].framework/Versions/A
[name].framework/Versions/A/Resources
[name].framework/Versions/A/Headers
[name].framework/Versions/Current -> A
[name].framework/Versions/A/[name] -> lib[name].so
[name].framework/Versions/A/lib[name].so -> lib[name].so.[version]
[name].framework/Versions/A/lib[name].so.[M] -> lib[name].so.[version]
Considering the current support for the -framework flag in gcc, this seems
reasonable. However, when one wants to emulate this flag for an aggregate
project where some elements depend on a previously built framework that's
part of the same project, it becomes tricky to refer to the correct location
for the framework headers.
We know that framework headers will always be referred to with
"<[name]/[header].h>" in the source files. So it would only make things
easier of the generated .framework bundle would respect that too and have
/Headers/[name] instead of /Headers alone.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=12575>
_______________________________________________
Message post� via/par Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
