From: testlaster@gmail.com (testlaster)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Writing makefiles for headers outside 'usr/include'
Date: Tue, 26 Aug 2014 10:09:57 +0200 [thread overview]
Message-ID: <53FC40D5.9070908@gmail.com> (raw)
So the initial problem I'm having is that wanting to use headers and
their libs like|module.h|and|init.d|and|pci.h|for instance can't be used
by simply going|#include <pci.h>|because if you check the
actual|pci.h|||(40 lines or so) file you will find that its allot
shorter then the usual dev|pci.h| so needless to say you can't use all
the functions. So now I have to use makefiles to point to other directories.
I've been trying to create makefiles but at the moment the errors just
rack up so much that I really don't know what part of the process is at
fault. Is it the C or the headers or the wrong libraries? I'm kind of
clueless to where the libraries might even be.
Could someone please help me write a makefile for Linux headers and
their libraries that is not in the usual|/usr/include|directory? The
source files that I want to use will be
in|usr/src/linux-headers-3.13.0.32-generic/include|. Also if they are in
the makefile how will I include them in the source?
I've been learning a lot of things in parallel and I think the curve is
starting to get to me. :/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140826/e170f78b/attachment-0001.html
next reply other threads:[~2014-08-26 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 8:09 testlaster [this message]
2014-08-26 8:31 ` Writing makefiles for headers outside 'usr/include' Anders Darander
2014-08-26 9:09 ` testlaster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53FC40D5.9070908@gmail.com \
--to=testlaster@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).