From: Chris R. <ch...@da...> - 2004-02-19 10:50:45
|
I ended up patching the OSX cpp - it's only a shell script. The patch can be found here: http://www.darkrock.co.uk/files/apple.cpp.patch It keeps the same behaviour but fixes the issues of passing the output file in as well as the input file. I did however need to make a commit to edje_cc to make sure that it did the legal thing and conformed to the right order of arguments. Chris On 18 Feb 2004, at 13:29, Nathan Ingersoll wrote: > Cpp on OS X requires that the input be passed on stdin. I have a change > in my local copy that does "cat file | cpp ...". I haven't committed > because others have seen a similar issue with gcc 3.3 under linux, but > that line did not fix the issue for them. My preference would be that > the CPP to be used is determined at configure time, rather than > requiring everyone to set a environment variable. > > On Wed, Feb 18, 2004 at 10:14:22AM +0000, Chris Ross wrote: >> Ok, >> >> So I am playing with edje under OSX. When edge_cc tries to compile the >> .edc's >> it chokes on OS X's cpp. I have made some changes to the source that >> give the >> default behaviour except if the environment variable EDJE_CPP is set. >> Anyone >> mind if I commit this change ? >> >> Chris > > > > -- > ----------------------------------------------------------------------- > - > | Nathan Ingersoll \\ Computer Systems & Network Coordinator > | > | nin...@ru... \\ http://www.ruralcenter.org > | > | http://ningerso.atmos.org/ \\ Rural Health Resource Center > | > ----------------------------------------------------------------------- > - > |