www.digitalmars.com         C & C++   DMDScript  

c++.idde - IDDE environment

reply "Matthew Wilson" <dmd synesis.com.au> writes:
Does the IDDE contain any DMC++-specific settings.

Basically, my problem is that I'm creating projects with relative include
directories. Some of these projects also need to see the DM STL directory.
Because I have several installations of the IDDE in order to support DM828,
DM829 and DMbeta I don't want to hard code the STL directory path. Also,
these projects will be downloadable once complete, and I don't want to
constrain users or require them to edit the projects.

When I'm using DMC++ from the command line I usually launch a command box
from a cmd script wherein the COMP_BASE and COMP_INC environment variables
are set to, say, P:\Programs\DM\DM828 and
P:\Programs\DM\DM828\Include;P:\Programs\DM\DM828\STL respectively.

Is this something I need to do in SC.INI maybe?

Any and all wisdom gratefully received

Matthew
Sep 22 2002
parent reply "Matthew Wilson" <dmd synesis.com.au> writes:
I've just looked more closely at SC.INI, which I've not changed since
installation, and the pertinent lines are

[Environment]
PATH=%PATH%;"% P%\..\bin"
BIN="% P%\..\bin"
INCLUDE="% P%\..\include";"% P%\..\mfc\include";"% P%\stl";%INCLUDE%
LIB="% P%\..\lib";"% P%\..\mfc\lib";%LIB%
HELP="% P%\..\help"

I presume that % P% is the installation directory, and further presume that
the IDDE infers this from its own execution path and defines it accordingly.
Given that, does anyone have any idea why I receive

 Fatal Error: blah-blah-blah: unable to open input file 'stl_config.h'

This file does indeed reside in the STL subdirectory immediately below the
DMC++ directory, and all other environment expansions appear to work.

Matthew


"Matthew Wilson" <dmd synesis.com.au> wrote in message
news:amlco3$2uca$1 digitaldaemon.com...

 Does the IDDE contain any DMC++-specific settings.

 Basically, my problem is that I'm creating projects with relative include
 directories. Some of these projects also need to see the DM STL directory.
 Because I have several installations of the IDDE in order to support


DM828,

 DM829 and DMbeta I don't want to hard code the STL directory path. Also,
 these projects will be downloadable once complete, and I don't want to
 constrain users or require them to edit the projects.

 When I'm using DMC++ from the command line I usually launch a command box
 from a cmd script wherein the COMP_BASE and COMP_INC environment variables
 are set to, say, P:\Programs\DM\DM828 and
 P:\Programs\DM\DM828\Include;P:\Programs\DM\DM828\STL respectively.

 Is this something I need to do in SC.INI maybe?

 Any and all wisdom gratefully received

 Matthew
Sep 22 2002
parent reply "Walter" <walter digitalmars.com> writes:
Does it work from the command line?

"Matthew Wilson" <dmd synesis.com.au> wrote in message
news:amld6n$2v10$1 digitaldaemon.com...

 I've just looked more closely at SC.INI, which I've not changed since
 installation, and the pertinent lines are

 [Environment]
 PATH=%PATH%;"% P%\..\bin"
 BIN="% P%\..\bin"
 INCLUDE="% P%\..\include";"% P%\..\mfc\include";"% P%\stl";%INCLUDE%
 LIB="% P%\..\lib";"% P%\..\mfc\lib";%LIB%
 HELP="% P%\..\help"

 I presume that % P% is the installation directory, and further presume


that

 the IDDE infers this from its own execution path and defines it


accordingly.

 Given that, does anyone have any idea why I receive

  Fatal Error: blah-blah-blah: unable to open input file 'stl_config.h'

 This file does indeed reside in the STL subdirectory immediately below the
 DMC++ directory, and all other environment expansions appear to work.

 Matthew
Sep 22 2002
next sibling parent "Matthew Wilson" <dmd synesis.com.au> writes:
Yes

"Walter" <walter digitalmars.com> wrote in message
news:amlghq$2b2$1 digitaldaemon.com...

 Does it work from the command line?

 "Matthew Wilson" <dmd synesis.com.au> wrote in message
 news:amld6n$2v10$1 digitaldaemon.com...

 I've just looked more closely at SC.INI, which I've not changed since
 installation, and the pertinent lines are

 [Environment]
 PATH=%PATH%;"% P%\..\bin"
 BIN="% P%\..\bin"
 INCLUDE="% P%\..\include";"% P%\..\mfc\include";"% P%\stl";%INCLUDE%
 LIB="% P%\..\lib";"% P%\..\mfc\lib";%LIB%
 HELP="% P%\..\help"

 I presume that % P% is the installation directory, and further presume


 that

 the IDDE infers this from its own execution path and defines it


 accordingly.

 Given that, does anyone have any idea why I receive

  Fatal Error: blah-blah-blah: unable to open input file 'stl_config.h'

 This file does indeed reside in the STL subdirectory immediately below




the

 DMC++ directory, and all other environment expansions appear to work.

 Matthew
Sep 22 2002
prev sibling next sibling parent reply "Matthew Wilson" <dmd synesis.com.au> writes:
Can the project include paths include environment variables, i.e. something
like

c:\mydir1;c:\mydir2;% P%\stl

perhaps?

"Walter" <walter digitalmars.com> wrote in message
news:amlghq$2b2$1 digitaldaemon.com...

 Does it work from the command line?

 "Matthew Wilson" <dmd synesis.com.au> wrote in message
 news:amld6n$2v10$1 digitaldaemon.com...

 I've just looked more closely at SC.INI, which I've not changed since
 installation, and the pertinent lines are

 [Environment]
 PATH=%PATH%;"% P%\..\bin"
 BIN="% P%\..\bin"
 INCLUDE="% P%\..\include";"% P%\..\mfc\include";"% P%\stl";%INCLUDE%
 LIB="% P%\..\lib";"% P%\..\mfc\lib";%LIB%
 HELP="% P%\..\help"

 I presume that % P% is the installation directory, and further presume


 that

 the IDDE infers this from its own execution path and defines it


 accordingly.

 Given that, does anyone have any idea why I receive

  Fatal Error: blah-blah-blah: unable to open input file 'stl_config.h'

 This file does indeed reside in the STL subdirectory immediately below




the

 DMC++ directory, and all other environment expansions appear to work.

 Matthew
Sep 22 2002
parent "Walter" <walter digitalmars.com> writes:
"Matthew Wilson" <dmd synesis.com.au> wrote in message
news:amlmmv$aln$1 digitaldaemon.com...

 Can the project include paths include environment variables, i.e.


something

 like

 c:\mydir1;c:\mydir2;% P%\stl

 perhaps?


No, but that might be a good idea.
Sep 28 2002
prev sibling parent "Matthew Wilson" <dmd synesis.com.au> writes:
Fixed it!

I mistakenly assumed the IDE deduced the requisite environment information
from its execution path. Walter steered my right, and now I've defined a CMD
file that simply creates the enviroment I want and then spawns SCWMN32.EXE.
Simple

Thanks again Walter

"Walter" <walter digitalmars.com> wrote in message
news:amlghq$2b2$1 digitaldaemon.com...

 Does it work from the command line?

 "Matthew Wilson" <dmd synesis.com.au> wrote in message
 news:amld6n$2v10$1 digitaldaemon.com...

 I've just looked more closely at SC.INI, which I've not changed since
 installation, and the pertinent lines are

 [Environment]
 PATH=%PATH%;"% P%\..\bin"
 BIN="% P%\..\bin"
 INCLUDE="% P%\..\include";"% P%\..\mfc\include";"% P%\stl";%INCLUDE%
 LIB="% P%\..\lib";"% P%\..\mfc\lib";%LIB%
 HELP="% P%\..\help"

 I presume that % P% is the installation directory, and further presume


 that

 the IDDE infers this from its own execution path and defines it


 accordingly.

 Given that, does anyone have any idea why I receive

  Fatal Error: blah-blah-blah: unable to open input file 'stl_config.h'

 This file does indeed reside in the STL subdirectory immediately below




the

 DMC++ directory, and all other environment expansions appear to work.

 Matthew
Sep 23 2002