Cross Platform method of importing files

2009-01-19 Thread Noam Rathaus
Hi, I would like to import into an existing project external XML files which will be used as internal data by the program I am compiling. The files need to be included each time I compile the program, and they tend to change quite frequently. Has anyone had experience building such a requireme

Re: Cross Platform method of importing files

2009-01-19 Thread Amos Shapira
2009/1/19 Noam Rathaus : > Hi, > > I would like to import into an existing project external XML files which will > be used as internal data by the program I am compiling. You mean you'd like to see the XML file converted into a C++ string compiled as part of the program? Probably a simple Perl sc

Re: Cross Platform method of importing files

2009-01-19 Thread Shachar Shemesh
Noam Rathaus wrote: Hi, I would like to import into an existing project external XML files which will be used as internal data by the program I am compiling. The files need to be included each time I compile the program, and they tend to change quite frequently. Has anyone had experience b

Re: Cross Platform method of importing files

2009-01-19 Thread Noam Rathaus
Amos, Thank you for the idea, I will look into that, how would you however import the files' content into the Makefile 'automatically' without to actually add it to it? Do you use a perl script to also modify the Makefile? On Monday 19 January 2009 14:39:28 Amos Shapira wrote: > 2009/1/19 Noam

Re: Cross Platform method of importing files

2009-01-19 Thread Noam Rathaus
Hi Shachar, I am talking about build-time import. Not open XML file and use its data :) Rather open an XML file during the build process and place the content found in it inside a 'string' (stl) object which will be later used by the program as data. On Monday 19 January 2009 15:17:04 Shachar

Re: Cross Platform method of importing files

2009-01-19 Thread ik
Hi Noam, I thought very hard if I should answer you... Anyway, look for resources in executible. You can change the context on a compiled executible without damaging the file itself, and you can load it properly. Ido On Mon, Jan 19, 2009 at 2:11 PM, Noam Rathaus wrote: > Hi, > > I would like

Re: Cross Platform method of importing files

2009-01-20 Thread Noam Rathaus
Hi Ido, Thank you for the answer, I will look into your idea. On Tuesday 20 January 2009 01:25:22 ik wrote: > Hi Noam, > > I thought very hard if I should answer you... > > Anyway, look for resources in executible. You can change the context > on a compiled executible without damaging the file it

Re: Cross Platform method of importing files

2009-01-20 Thread Shachar Shemesh
Noam Rathaus wrote: Amos, Thank you for the idea, I will look into that, how would you however import the files' content into the Makefile 'automatically' without to actually add it to it? Do you use a perl script to also modify the Makefile? What build system are you using? If you are us

Re: Cross Platform method of importing files

2009-01-20 Thread Shlomi Fish
On Tuesday 20 January 2009 10:52:08 Shachar Shemesh wrote: > Noam Rathaus wrote: > > Amos, > > > > Thank you for the idea, I will look into that, how would you however > > import the files' content into the Makefile 'automatically' without to > > actually add it to it? > > > > Do you use a perl scr

Re: Cross Platform method of importing files

2009-01-20 Thread Shachar Shemesh
Shlomi Fish wrote: Just a note - from my experience it's not such a good idea to use redirection to the target file inside make. That is correct. A better idea would be to call: ./convert.pl -o $@ $< A simpler method is: ./convert.pl < $< > $...@.tmp

Re: Cross Platform method of importing files

2009-01-20 Thread Oron Peled
On Tuesday, 20 בJanuary 2009, Shlomi Fish wrote: > On Tuesday 20 January 2009 10:52:08 Shachar Shemesh wrote: > > xmldata.cpp: xmldata.xml > >convert.pl < $< > $@ > Just a note - from my experience it's not such a good idea to use > redirection to the target file inside make. Th

Re: Cross Platform method of importing files

2009-01-20 Thread Valery Reznic
> Some programs input/output only via stdin/stdout (e.g: > tr(1)) > One common solution to this issue is: > >target: prerequisites... > prog < $< > $@ || rm -f $@ > It's not good - even if prog fail, mail will be thinking that whole command finished successfully. I do it this