Displaying 3 results from an estimated 3 matches for "shobj_path".
2007 Jul 19
6
[LLVMdev] PATH and LD_LIBRARY_PATH
...s. The functions take care of the
details.
However, even with only a single checkout (environment) of llvm
software, there are details to be taken care of. We would like to
support this better, but the question is how.
Here are some of the issues:
* On some platforms you set SHLIB_PATH or SHOBJ_PATH, etc.
* With more modules the PATH and LD_LIBRARY_PATH become long (one
entry per module). Having every module's Debug/bin in PATH and
Debug/lib in LD_LIBRARY_PATH gets hard to maintain when there's
multiple environments. Furthermore, the paths need to change...
2007 Jul 20
0
[LLVMdev] PATH and LD_LIBRARY_PATH
...ach module.
Ok.
> However, even with only a single checkout (environment) of llvm
> software, there are details to be taken care of. We would like to
> support this better, but the question is how.
>
> Here are some of the issues:
> * On some platforms you set SHLIB_PATH or SHOBJ_PATH, etc.
This is up to the user to know what to do.
> * With more modules the PATH and LD_LIBRARY_PATH become long (one
> entry per module). Having every module's Debug/bin in PATH and
> Debug/lib in LD_LIBRARY_PATH gets hard to maintain when there's
> m...
2007 Jul 20
1
[LLVMdev] PATH and LD_LIBRARY_PATH
...wever, even with only a single checkout (environment) of llvm
> > software, there are details to be taken care of. We would like to
> > support this better, but the question is how.
> >
> > Here are some of the issues:
> > * On some platforms you set SHLIB_PATH or SHOBJ_PATH, etc.
>
> This is up to the user to know what to do.
>
> > * With more modules the PATH and LD_LIBRARY_PATH become long (one
> > entry per module). Having every module's Debug/bin in PATH and
> > Debug/lib in LD_LIBRARY_PATH gets hard to maintain...