This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Getting "can't open include file" upon InstallScript compile.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2009
02:25 PM
Getting "can't open include file" upon InstallScript compile.
I am using InstallShield 2009 on an InstallScript project. I have a utility script, SetFileAssociations.rul, in a common directory. I have the main Setup.rul, and at the top I have:
#include "ifx.h"
#include "SetFileAssociations.rul"
I am getting "fatal error F8511: can't open include file"
Background - this is a new project, and I have 10 other InstallScript projects where I am doing exactly the same thing (same file in same location, inserted into Files). Those 10 are all working. I do remember there was something tricky about getting it to work, but I inserted the file, and the path variable is defined properly in the project.
If I import the file, it of course works. However, I do not want to carry a copy of the file in multiple places.
If I use a relative path in the include statement, it works. That seems clunky, and should not be necessary.
It seems like the project is not resolving the path variable at compile time. I have compared the setup.rul files as well as project files from projects that work, and cannot see anything obvious that would cause it not to work.
Ideas? Why is it working 10 out of 11 times?
#include "ifx.h"
#include "SetFileAssociations.rul"
I am getting "fatal error F8511: can't open include file"
Background - this is a new project, and I have 10 other InstallScript projects where I am doing exactly the same thing (same file in same location, inserted into Files). Those 10 are all working. I do remember there was something tricky about getting it to work, but I inserted the file, and the path variable is defined properly in the project.
If I import the file, it of course works. However, I do not want to carry a copy of the file in multiple places.
If I use a relative path in the include statement, it works. That seems clunky, and should not be necessary.
It seems like the project is not resolving the path variable at compile time. I have compared the setup.rul files as well as project files from projects that work, and cannot see anything obvious that would cause it not to work.
Ideas? Why is it working 10 out of 11 times?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2009
09:15 PM
You should be able to add the path variable reference to the include paths in Build->Settings to ensure the path is used by the compiler to search for files referenced by #include.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 23, 2009
09:09 AM
Josh - All I can say is "Doh!"
That was the "trick" I figured out last time, and I have no idea how I stumbled into it then. Maybe it is too obvious - using an include, need to set the path! It would be nice if the help mentioned it in the area where it compares and contrasts "Insert" and "Import" for script files.
Thanks for the help!
That was the "trick" I figured out last time, and I have no idea how I stumbled into it then. Maybe it is too obvious - using an include, need to set the path! It would be nice if the help mentioned it in the area where it compares and contrasts "Insert" and "Import" for script files.
Thanks for the help!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2009
03:40 PM
An almost funny addendum:
As soon as I add to the compiler include path, the master include file "ifx.h" cannot be found anymore, i.e. the standard "default include directory" seems to be somehow overwritten or removed from the path. Is this known? :rolleyes:
Since ..\ instead - being relative to the other standard include folder only works as long the current directory points to the location of the .ism I'd like to use but it isn't possible that way.
As soon as I add
Since ..\ instead - being relative to the other standard include folder
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)