|
From: | Jeremy Bettis |
Subject: | Frameworks on windows. |
Date: | Mon, 27 Jun 2005 21:02:39 -0500 |
Let me share a few ideas here before I send in a
patch so I can judge the likelyhood of it being accepted.
Assumptions:
*) Frameworks depend heavily on symbolic links. (in
gnustep-make)
*) Windows (Mingw environment) has no symbolic
links
*) The Foo.framework/Versions/A/... is probably not
worth supporting w/o symlinks.
*) Gcc (non-apple) doesn't support the -F or
-framework options, and on windows probably never will.
So I have put in a number of ifeq($(HAS_LN_S),no)
type statements into gnustep-make to have it simply not use the Versions stuff
at all.
Next problem, before installation, the framework
can't find it's own headers, since again the ln -s ../Foo.framework/Headers
derived_sources/Headers/Foo fails. I had a complex hack that generated an
#include "../Foo.Frameworks/Headers/filename.h"for each file, but now I think a
better idea would be to have the headers go into
Foo.framework/Headers/Foo/filename.h right from the start.
If I send in a patch to do the above, in theory,
would it be acceptable?
|
[Prev in Thread] | Current Thread | [Next in Thread] |