Re: Problem with C++ module creation using INCLUDE env. variable -- C400-L

Dennis Lovelady <iseries@...> writes:

I finally got the opportunity to play with this. INCLUDE values that did
not work for me:
./include
include

But both of these worked for me:
./include/
include/

I hope it's that simple for you!

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Change is inevitable, except from a vending machine.

it is running interactively.

OK, then it's not because the environment variables are not being
copied to the batch job (see CPYENVVAR keyword on SBMJOB command for
more information).

I think it's perhaps because of the complicated relationships between
SRCSTMF, INCDIR, OPTION, and the INCLUDE environment variable. Note
that I don't use source stream files but I note from the C/C++
Compiler Reference (for VRM610):

Chapter 4. Page 85

2. If SRCSTMF is specified, then the following compiler options
are
ignored:
o INCDIR( )
o OPTION(*INCDIRFIRST)
o TEXT(*SRCMBRTXT)
o OPTION(*STDINC)
o OPTION(*SYSINCPATH)

Note that INCDIR is ignored in this case (seems peculiar behaviour to
me so perhaps the documentation is wrong on this point. It also
contradicts the C/C++ Programmer's Guide). Note also that
OPTION(*INCDIRFIRST) is ignored; this is relevant to the next item
(but also seems wrong to me).

Chapter 4. Page 90

*NOINCDIRFIRST
Default setting. The compiler searches for user include files in
the root
source directory first, and then in the directories specified by
the
INCDIR option.

*INCDIRFIRST
The compiler searches for user include files as follows:
1. If you specify a directory in the INCDIR parameter, the
compiler
searches for file_name in that directory.
2. If more than one directory is specified, the compiler searches
the directories in the order that they appear on the command
line.
3. Searches the directory where your current root source file
resides.
4. If the INCLUDE environment variable is defined, the compiler
searches
the directories in the order they appear in the INCLUDE path.
5. If the *NOSTDINC compiler option is not chosen, search the
default
include directory /QIBM/include.

Note that the only mention of the INCLUDE environment variable is when
*INCDIRFIRST is specified. The documentation implies that with
*NOINCDIRFIRST specified only the source directory and the INCDIR
directories are searched.

Chapter 4. Page 129

INCDIR
Lets you redefine the path used to locate include header files
when
compiling a source stream file. This option is ignored if the
source
file's location is not defined as an IFS path with the SRCSTMF
compiler
option, or if the full absolute path name is specified on the
#include
directive.

Note that the above contradicts point 2 on page 85.

Given that the documentation states that when SRCSTMF is used both
INCDIR and OPTION(*INCDIRFIRST) are ignored then the implication is
that the default behaviour i.e., OPTION(*NOINCDIRFIRST) is in effect.

If that is true and point 2 on page 85 is correct then you cannot use
this combination.

However, it seems to me that ignoring INCDIR and OPTIONS(*INCDIRFIRST)
defeats the point of these things. Perhaps you actually have to
specify OPTIONS(*INCDIRFIRST) to get the INCLUDE environment variable
to be processed?

I note that Dennis said in an earlier append that "the INCLUDE
environment variable is ignored if INCDIR is specified" but I couldn't
find that. Indeed, I found the opposite in the Programmer's Guide:

Chapter 17. Page 206

1. Searches the directory where your current source file resides.
The
current source file is the one that contains the directive
#include "file_name".
2. If you specify a directory in the INCDIR parameter, the
compiler
searches for file_name in that directory.
3. If more than one directory is specified, the compiler searches
the directories in the order that they appear on the command
line.
4. If the INCLUDE environment variable is defined, the compiler
searches the directories in the order they appear in the INCLUDE
environment variable.
5. Searches the directory /QIBM/include.

So, aside from the confusing documentation, it seems what you want
should work and is perhaps failing due to a combination of parameters.
Perhaps also it is "silliness" with regard to the value in the INCLUDE
variable itself. I know some Unix-y stuff expects a trailing colon on
path lists so try adding that. Also, perhaps the use of ./ is
confusing things. Since it just means the current path (.. = parent, .
= current) and since a relative path will start in the current
directory any way perhaps removing that will fix things.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------

--
This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@...
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@...
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.

All,
thanks a lot for your involvement, but for me it still does not work.

(It is really extremely frustrating for me that IBMâs C/C++ guides are so
confusing.)

I have done the following test.

The compilation environment and source code details:
(1) OS version: 5.3;
(2) IFS structure:
/my_dir/my_project/syscsrc/
/my_dir/my_project/include/syscinc/
(3) current directory:
/my_dir/my_project
(4) source code mod_name.cpp with #include directive:
LINE 10: #include "syscinc/sys006i.hpp"

Tests done:
0. using INCLUDE env. variable:

CRTCPPMOD MODULE(my_lib/mod_name)
SRCSTMF('syscsrc/mod_name.cpp')
OUTPUT(*PRINT)
with:
(1) INCLUDE './include/'
(2) INCLUDE './include/:'
(3) INCLUDE './include'
(4) INCLUDE './include:'
(5) INCLUDE 'include/'
(6) INCLUDE 'include/:'
(7) INCLUDE 'include'
(8) INCLUDE 'include:'
(9) INCLUDE '/my_dir/my_project/include/'
(10)INCLUDE '/my_dir/my_project/include/:'
(11)INCLUDE '/my_dir/my_project/include'
(12)INCLUDE '/my_dir/my_project/include:'

THE COMPILATION FAILED with the message:
"syscsrc/mod_name.cpp", line 10.10: CZP0836(30) The #include
file "syscinc/sys006i.hpp" is not found.

1. using INCLUDE env. variable:

CRTCPPMOD MODULE(my_lib/mod_name)
SRCSTMF('syscsrc/mod_name.cpp')
OUTPUT(*PRINT)
OPTION(*INCDIRFIRST)
with:
(1) INCLUDE './include/'
(2) INCLUDE './include/:'
(3) INCLUDE './include'
(4) INCLUDE './include:'
(5) INCLUDE 'include/'
(6) INCLUDE 'include/:'
(7) INCLUDE 'include'
(8) INCLUDE 'include:'
(9) INCLUDE '/my_dir/my_project/include/'
(10)INCLUDE '/my_dir/my_project/include/:'
(11)INCLUDE '/my_dir/my_project/include'
(12)INCLUDE '/my_dir/my_project/include:'

THE COMPILATION FAILED with the message:
"syscsrc/mod_name.cpp", line 10.10: CZP0836(30) The #include
file "syscinc/sys006i.hpp" is not found.

2. using INCDIR command parameter:

CRTCPPMOD MODULE(my_lib/mod_name)
SRCSTMF('syscsrc/mod_name.cpp')
OUTPUT(*PRINT)
with:
(1) INCDIR('./include')
(2) INCDIR('./include/')
(3) INCDIR('include')
(4) INCDIR('include/')
(5) INCDIR('/my_dir/my_project/include/')
(6) INCDIR('/my_dir/my_project/include')

Module MOD_NAME was CREATED in library MY_LIB

Either I am doing something which is 'completely stupid' (and I am not able to
find it) or the INCLUDE env. variable is ignored by the compiler.

Dennis,
can you please provide me with the following your test's details/parameters?

1. OS version
2. IFS directory structure, where the source and include files exist;
3. the current directory name;
4. compilation command;
5. source code snapshot with #include directive

Thanks,
Darek