From: Francesco M. <f18...@ya...> - 2005-07-06 23:11:54
|
Hi, >>>I've tried to set the environment variable >>>$(WXCODE)=c:\wxCVS\wxCode\wxCode and then use it like this in a dsw >>>file for a project that will link to a number of different libraries. >>>############################################################################### >>>Project: "wxSheetLib_wx26"=$(WXCODE)\components\wxsheet\src\sheetlib_wx26.dsp >>>- Package Owner=<4> > > ############################################################################### > >>>When I start MSVS it complains about not being able to find >>>c:\wxCVS\Plotto\$(WXCODE)\components\wxsheet\src\sheetlib_wx26.dsp >>>The first part of the dir "c:\wxCVS\Plotto\" is the location of the >>>dsw file that was loaded (putting quotes around it doesn't do >>>anything). If I go back to relative paths it works just fine. Is there >>>a way to make it use absolute paths so that the $(WXCODE) env var can >>>be set once and work for any project in any directory? > > >>I'm not sure to understand what you want to do... but I think that >>c:\wxCVS\Plotto\$(WXCODE)\components\wxsheet\src\sheetlib_wx26.dsp >>should be changed to >>$(WXCODE)\components\wxsheet\src\sheetlib_wx26.dsp > > > Maybe I wasn't clear, MSVS is adding the path that the dsw file was > opened in all by itself! You'll see that above I specify the directory > of wxsheetlib_wx26.dsp file without the "c:\wxCVS\Plotto". > > I need a way to make MSVS to open this as an absolute path. (not > relative to the dsw file that contains this line) > > Project: "wxSheetLib_wx26"=$(WXCODE)\components\wxsheet\src\sheetlib_wx26.dsp which VS version are you using ? I created a file (by hand) name wxsheet.dsw with the contents: ========wxsheet.dsw===================== Microsoft Developer Studio Workspace File, Format Version 6.00 # WARNING: DO NOT EDIT OR DELETE THIS WORKSPACE FILE! ############################################################################### Project: "wxSheetLib_wx26"=$(WXCODE)\components\wxsheet\src\sheetlib_wx26.dsp - Package Owner=<4> Package=<5> {{{ }}} Package=<4> {{{ }}} ========eof===================== and with MSVC++ 6.0 it opens up perfectly with WXCODE=t:\wxCode (my path to the wxCode folder).... another advice is: use bakefile to generate your DSW/DSP files ;-) >>PS: can you chmod the readme.txt in /home/groups/w/wx/wxcode/htdocs so >>that anyone of the wxCode group can access it (chmod g+rwx readme.txt) ? >>I'll update it... > > > Done. You mean chmod g+rw, right? I notice that just about all the > files are executable, it's probably best to -x any of them that aren't > scripts. I have removed the x flag from non-scripts file; However I also need to have write permissions on the "template" folder of the wxCode CVS. The file CVSROOT\avail needs to be modified to allow me to work on wxCode\template and only you & Otto can do that... For more info about "template" see http://wxcode.sourceforge.net/rules.php, rule #1 It will contain all the usual stuff & folder structure of a typical component... Francesco |