PDA

View Full Version : can't open setup.inx in build batch script



NewsArchive
01-04-2002, 01:00 AM
I am attempting to automatically compile/build an InstallShield project
using a batch script (unaltered) generated by the 'Build/export [build]
batch file...' feature of InstallShield Professional 6.21. While in
InstallShield, the project compiles and builds fine, however, when I attempt
to run the batch script I receive the following output:
/*
*D:\IS\Websense Reporter 6.3>test
*InstallShield Script Compiler
*Version 6.21.100.1396
*Copyright (c) 1990-1998 InstallShield Software Corporation
*
*Compiling...
*setup.rul
*D:\IS\Websense Reporter 6.3\Script Files\setup.rul(601) : fatal error
F8511: can't open include file
*setup.inx - 1 error(s), 0 warning(s)
*/

In an attempt to resolve this error, I added an include (-i) of
IS6.3\Include (where IS6.3 is program files\install shield etc) which is the
path to the sddialogue.h file (line 2 of setup.rul) Running the batch file
after adding this include results in 51 errors, originating from winsub.h ->
identifier already defined (10 or so), instdlg.rul -> undefined identifier
(10 or so), and askLanguage.idd -> undefined identifier warnings as well as
a string value required.
Copying 'sddialogue.h' from the InstallShield Include directory into my
'Script Files' project directory allows for a sucessful compile/build.

Are there any suggestions as to why this is occuring, and how I may
resolve it in a cleaner manner? Any thoughts on why including
InstallShield's include directory is creating a problem? Does include take
the first file found, or does it keep searching, and include all files it
encounters or something to that effect?
Any feedback would be appreciated. Please feel free to e-mail me at
wralphs@websense.com.
Thank you,
Will Ralphs

NewsArchive
01-07-2002, 01:00 AM
Can you compile inside the IDE? It sounds like you have included a file that
the compiler can't find.

Dave Stiff
Trango Software

"Will Ralphs" <wralphs@websense.com> wrote in message
news:3c3633f7$1@news.installshield.com...
> I am attempting to automatically compile/build an InstallShield project
> using a batch script (unaltered) generated by the 'Build/export [build]
> batch file...' feature of InstallShield Professional 6.21. While in
> InstallShield, the project compiles and builds fine, however, when I
attempt
> to run the batch script I receive the following output:
> /*
> *D:\IS\Websense Reporter 6.3>test
> *InstallShield Script Compiler
> *Version 6.21.100.1396
> *Copyright (c) 1990-1998 InstallShield Software Corporation
> *
> *Compiling...
> *setup.rul
> *D:\IS\Websense Reporter 6.3\Script Files\setup.rul(601) : fatal error
> F8511: can't open include file
> *setup.inx - 1 error(s), 0 warning(s)
> */
>
> In an attempt to resolve this error, I added an include (-i) of
> IS6.3\Include (where IS6.3 is program files\install shield etc) which is
the
> path to the sddialogue.h file (line 2 of setup.rul) Running the batch
file
> after adding this include results in 51 errors, originating from
winsub.h ->
> identifier already defined (10 or so), instdlg.rul -> undefined identifier
> (10 or so), and askLanguage.idd -> undefined identifier warnings as well
as
> a string value required.
> Copying 'sddialogue.h' from the InstallShield Include directory into my
> 'Script Files' project directory allows for a sucessful compile/build.
>
> Are there any suggestions as to why this is occuring, and how I may
> resolve it in a cleaner manner? Any thoughts on why including
> InstallShield's include directory is creating a problem? Does include
take
> the first file found, or does it keep searching, and include all files it
> encounters or something to that effect?
> Any feedback would be appreciated. Please feel free to e-mail me
at
> wralphs@websense.com.
> Thank you,
> Will Ralphs
>
>

NewsArchive
01-07-2002, 01:00 AM
Yes, the project compiles fine from within the IDE. The problem is that
InstallShield can not locate the file: 'sddialogue.h'. The problem I am
having is that adding the path to that file (program files\install
shield\install Shield 6.0\include) results in a good many other errors which
are unrelated. Copying the file to my setup scripts directory allows it to
compile, however, that is not where it should be getting this file from.
(It's an Install Shield file... I vote it stay in the Install Shield
directory)
Thanks,
Will


David Stiff <davids@trangosoft.com> wrote in message
news:3c39e58e$1@news.installshield.com...
> Can you compile inside the IDE? It sounds like you have included a file
that
> the compiler can't find.
>
> Dave Stiff
> Trango Software
>
> "Will Ralphs" <wralphs@websense.com> wrote in message
> news:3c3633f7$1@news.installshield.com...
> > I am attempting to automatically compile/build an InstallShield project
> > using a batch script (unaltered) generated by the 'Build/export [build]
> > batch file...' feature of InstallShield Professional 6.21. While in
> > InstallShield, the project compiles and builds fine, however, when I
> attempt
> > to run the batch script I receive the following output:
> > /*
> > *D:\IS\Websense Reporter 6.3>test
> > *InstallShield Script Compiler
> > *Version 6.21.100.1396
> > *Copyright (c) 1990-1998 InstallShield Software Corporation
> > *
> > *Compiling...
> > *setup.rul
> > *D:\IS\Websense Reporter 6.3\Script Files\setup.rul(601) : fatal error
> > F8511: can't open include file
> > *setup.inx - 1 error(s), 0 warning(s)
> > */
> >
> > In an attempt to resolve this error, I added an include (-i) of
> > IS6.3\Include (where IS6.3 is program files\install shield etc) which is
> the
> > path to the sddialogue.h file (line 2 of setup.rul) Running the batch
> file
> > after adding this include results in 51 errors, originating from
> winsub.h ->
> > identifier already defined (10 or so), instdlg.rul -> undefined
identifier
> > (10 or so), and askLanguage.idd -> undefined identifier warnings as well
> as
> > a string value required.
> > Copying 'sddialogue.h' from the InstallShield Include directory into
my
> > 'Script Files' project directory allows for a sucessful compile/build.
> >
> > Are there any suggestions as to why this is occuring, and how I may
> > resolve it in a cleaner manner? Any thoughts on why including
> > InstallShield's include directory is creating a problem? Does include
> take
> > the first file found, or does it keep searching, and include all files
it
> > encounters or something to that effect?
> > Any feedback would be appreciated. Please feel free to e-mail me
> at
> > wralphs@websense.com.
> > Thank you,
> > Will Ralphs
> >
> >
>
>

rrussell
01-10-2004, 11:12 PM
Hi all,
I wanted to post a reply to all this business regarding setup.inx. I was having this same exact problem. The main symptoms were that I could compile in the IDE but not via my build script. I kept getting an error saying '...\setup.rul(13) : Fatal error F8511: can't open include file
setup.inx - 1 error...
Well I spent so much time worried about the setup.inx file I glossed over the fact that it was spitting out the error line (13) in the setup.rul file. Turns out line 13 was including a file called 'sddialog.h' which apparently the IDE had resolved the path to but the build script shell had not. When I commented out this line (and the associated include 'sddialog.rul' at the bottom of setup.rul) then I could compile from the shell. Hope this helps some other poor sucker. The logging error related to setup.inx seems to be a red herring in this case.

ROb