- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
How can i use a environment variable to hold the include
statement flexible.
statement flexible.
Enlace copiado
2 Respuestas
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
Sorry, you can't. But you can specify include paths under Project..Settings..Fortran..Preprocessor or /include on the command line.
Steve
Steve
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
We use relative paths and environment variables in the "Fortran -> Preprocesser -> INCLUDE and USE Paths:"
Mine is:
"..Includes;$(WCERT)SourceIncludes"
On my machine WCERT = "m:" and is where our latest released build source resides. ( is the current product I am working on. )
All of our source is in folders under "x:source".
So all includes are in "x:sourceincludes".
(x: is wherever the user has put his copy of the latest build; the folder layout is the same for release and testing of a)
This allows programmers to put their testing on different drives and allows for the programmer to only have copies of whatever they have changed.
It also allows the programmer to take a copy of the entire under test and move it to another machine and start right up and go after defining WCERT.
We also use WCERT to point to where the libraries are.
( "Properties" of an added library, "Persist as:" name would be something like "$(wcert)LibDebugGEN_UTIL.lib". )
Mine is:
"..Includes;$(WCERT)SourceIncludes"
On my machine WCERT = "m:
All of our source is in folders under "x:
So all includes are in "x:
(x: is wherever the user has put his copy of the latest build; the folder layout is the same for release and testing of a
This allows programmers to put their testing on different drives and allows for the programmer to only have copies of whatever they have changed.
It also allows the programmer to take a copy of the entire
We also use WCERT to point to where the libraries are.
( "Properties" of an added library, "Persist as:" name would be something like "$(wcert)LibDebugGEN_UTIL.lib". )

Responder
Opciones de temas
- Suscribirse a un feed RSS
- Marcar tema como nuevo
- Marcar tema como leído
- Flotar este Tema para el usuario actual
- Favorito
- Suscribir
- Página de impresión sencilla