[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #12575] suggestion about header files in frameworks

From: Wolfgang Sourdeau
Subject: [bug #12575] suggestion about header files in frameworks
Date: Wed, 6 Apr 2005 03:04:34 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.6) Gecko/20050401 Firefox/1.0.2 (Debian package 1.0.2-2)


                 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



The current filesystem infrastucture for frameworks is a follows:

[name].framework/Headers -> Versions/Current/Headers
[name].framework/Resources -> Versions/Current/Resources
[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:


  Message posté via/par Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]