[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #12575] suggestion about header files in frameworks
From: |
Nicola Pero |
Subject: |
[bug #12575] suggestion about header files in frameworks |
Date: |
Wed, 6 Apr 2005 12:05:49 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 |
Update of bug #12575 (project gnustep):
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
Having looked into that again, I think we don't need to change the header
structure because you can already access the framework headers as required by
using ...
-I<path to the framework build dir>/derived_src
derived_src already contains the headers in the form <name>/<header> so that
by using -I<path to the framework build dir>/derived_src you should be able
to use the framework headers in other parts of the same project.
Eg, if you have
MyFramework
MyApplication
and you compile MyFramework before MyApplication, you can access
MyFramework's headers from MyApplication by adding
-I../MyFramework/derived_src
#include <MyFramework/MyHeader.h>
That should work well :-)
Thanks for your feedback! Much appreciated :-)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=12575>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/