Re: [E-devel] [PATCH] edje_cc C-preprocessor invocation

2006-01-06 Thread The Rasterman
On Wed, 21 Dec 2005 10:01:41 -0600 Nathan Ingersoll <[EMAIL PROTECTED]> babbled: > I think you committed the earlier version of the patch that didn't work > correctly. The later one had a redirected output that solved some issues on > MacOS 10.3. fixed... i'll commt as soon as i have net access :

Re: [E-devel] [PATCH] edje_cc C-preprocessor invocation

2005-12-21 Thread Nathan Ingersoll
I think you committed the earlier version of the patch that didn't work correctly. The later one had a redirected output that solved some issues on MacOS 10.3.On 12/20/05, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: On Tue, 20 Dec 2005 02:13:14 -0800 Jon Merriman <[EMAIL PROTECTED]>

Re: [E-devel] [PATCH] edje_cc C-preprocessor invocation

2005-12-20 Thread The Rasterman
On Tue, 20 Dec 2005 02:13:14 -0800 Jon Merriman <[EMAIL PROTECTED]> babbled: > Here's a patch that changes how edje_cc invokes the C pre-processor > so that it does not break on systems with the BSD cpp wrapper in the > default path. Before, cpp would return 1 and compile() would continue >

Re: [E-devel] [PATCH] edje_cc C-preprocessor invocation

2005-12-20 Thread Jon Merriman
On Dec 20, 2005, at 6:38 AM, Nathan Ingersoll wrote: Have you verified this works on MacOS 10.3? Last I checked it insists that input is on stdin. You're right. It seems that 10.3's behavior was incorrect; it ignored the second non-option argument. So far the only way that seems to work

Re: [E-devel] [PATCH] edje_cc C-preprocessor invocation

2005-12-20 Thread Nathan Ingersoll
Have you verified this works on MacOS 10.3? Last I checked it insists that input is on stdin. So far the only way that seems to work on both 10.3 and 10.4 is to pipe input on stdin and redirect output to the file. Something like: cat %s | cpp -I%s %s > %sI have not tested this on non MacOS systems