Re: How to stringify a CPP macro

2010-04-14 Thread Pavel Sanda
Stephan Witt wrote: > It has to be passed from outside to configure. > Like ./configure --aspell-framework-name=Aspell.framework > > Currently I cannot do that (missing knowledge) and so I do > CPPFLAGS="-DASPELL_FRAMEWORK=Aspell.framework" ./configure > instead. i dont have the knowledge either

Re: How to stringify a CPP macro

2010-04-13 Thread Stephan Witt
Am 13.04.2010 um 11:35 schrieb Jean-Marc Lasgouttes: > Stephan Witt writes: > >> I'm looking for a tighter coupling of the build script and the compiled code. >> There has to be a strict coherence between the strings the build script uses >> and the strings for runtime lookup by LyX binary. So I

Re: How to stringify a CPP macro

2010-04-13 Thread Jean-Marc Lasgouttes
Stephan Witt writes: > I'm looking for a tighter coupling of the build script and the compiled code. > There has to be a strict coherence between the strings the build script uses > and the strings for runtime lookup by LyX binary. So I want to pass a define > here. To convert it to a string I co

Re: How to stringify a CPP macro

2010-04-13 Thread Stephan Witt
Am 13.04.2010 um 09:03 schrieb Sam Liddicott: > Your stringify looks ok. Yes, I have tested it and it works. But I know there are guys out there who are not comfortable with preprocessor "hacks". So I'm asking for an alternate solutions if it exists... > -DSTR_ASPELL_FRAMEWORK="x.y" probably

Re: How to stringify a CPP macro

2010-04-13 Thread Sam Liddicott
Your stringify looks ok. -DSTR_ASPELL_FRAMEWORK="x.y" probably didn't work because of the shell eating the quotation marks. -DSTR_ASPELL_FRAMEWORK='"x.y"' might have worked as far as invoking the makefile, but when it invoked the compiler you may then loose the remaining quote marks (unless