CFLAGS directives get hardwired?

Thread View: comp.sys.next.programmer

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by & Garrett Fri, 11 Sep 1992 20:55

#984

Author: & Garrett
Date: Fri, 11 Sep 1992 20:55

25 lines
1817 bytes

This is a general question about the compiler, CFLAGS and directories and  
not just about Sybase dblibrary, so don't stop reading.  I have an app  
that uses a lot of Sybase dblibrary calls.  In my Makefile.preamble I have  
this line:

CFLAGS = -I/usr/sybase/include -L/usr/sybase/lib

	When I build the project and run it on my machine, everything  
works fine.  We have some machines at another site, and their mounts are  
different so that their SYBASE directory is /Exports/usr/local/sybase  
instead of /usr/sybase.  When they run the app there, it doesn't work (an  
error message says dblibrary can't find one of the files it needs in that  
directory).  When I hack a soft link on one of those machines from  
/usr/sybase to /Exports/usr/local/sybase, everything works fine.
	I don't understand a lot about the compiler, but I can't see why,  
after it's successfully found these header files and libraries at compile  
time, it hardwires these paths into the executable so that it only looks  
in those directories at run time.  Why not depend on PATH?  Is it  
unreasonable of me to want to be able to run something on a machine that  
doesn't have a directory structure exactly the same as the one on which it  
was compiled?
	What can I do?  Thanks in advance for any insight or help.

Colin Garrett
NeXTMail: colin@delphi.bsd.uchicago.edu

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads