🚀 go-pugleaf

Jan Seiffert wrote:

> These are not messages from gcc not finding a header, these are messages from
> the linker ("ld returned 1 exit status"). When you header contains more than
> just a bunch of defines and datatypes, you need the coresponding object files
> where the compiled code of the defined functions reside. Either as object files
> (.o), archive (.a) or shared library (.so).
> You have to pass them on the link line. Please look at the Manual for the
> options -L and -l (for .o's you need no options).
> 
> Look around in your Ubuntu System, you have /usr/include, a bunch of system
> header files (text only), and /usr/lib, where the librarys for the system libs
> reside (the binaries).
> Where you put your project stuff, thats up to you. As long as your project is
> not part of the installed System, it has no business in writing to the system paths.
> 
> Maybe before you "unleash" C, you want to read a tutorial on how building
> software under Unix works (or more concrete the classic multipart C stack:
> preprocessor, compiler, assembler, linker), because you just ran into the "what?
> a header is not the complete lib"-FAQ
> 
>> So, I decide to put
>> the header where gcc *is* looking, but ubuntu won't let me put a header
>> in any of the directories that are included in the search.
>>
> 
> Because these are system directories, you need the right permission to do so.
> Something with "sudo cp ..."
> 
>> Question 1:  Where am I supposed to put home-rolled headers when I
>> compile with gcc on ubuntu?
>>
> 
> Right beside the rest of your project, no need to put them somewhere else.


Thanks, Jan, everything you write here is correct and helpful.
-- 
frank