Bug 3904 - generated packages are not relocatable.
: generated packages are not relocatable.
Status: RESOLVED FIXED
: C WS Core
Bindings Generation
: development
: PC Linux
: P3 normal
: 4.0.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-11-10 10:08 by
Modified: 2005-11-10 13:55 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-11-10 10:08:03
when a package is the following is put in the metadata:

<Build_Environment><cflags>@GPT_PKG_CFLAGS@
-I@GLOBUS_INSTALLDIR@/include/@GLOBUS_FLAVOR_NAME@/wsrf/services
-I@GLOBUS_INSTALLDIR@/include/@GLOBUS_FLAVOR_NAME@/</cflags><external_includes>@GPT_EXTERNAL_INCLUDES@</external_includes><external_libs>@GPT_EXTERNAL_LIBS@</external_libs>

this will ultimately resolve to an absolute path in the globus location,
therefore, if you install a service into 1 $GL then relocate the $GL to a new
path the meta data will still hold references to the old path.
------- Comment #1 From 2005-11-10 13:55:37 -------
Committed a fix to cgen (changed the offending lines in the template to use
\\\$(GLOBUS_LOCATION) in place of @GLOBUS_INSTALLDIR@. Also changed the packages
which were based on cgen packages to use the correct path string.

joe