From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Mini build while experimenting with C programming?
Date: Mon, 23 Dec 2024 12:23:38 +0100 [thread overview]
Message-ID: <E7B09BE4-0F4D-433F-B16E-69775905CD2B@ipfire.org> (raw)
In-Reply-To: <57FC3509-B2F7-4F9A-B83D-131180796AA7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Hello Jon,
The easiest way to do this is to run the entire build from next or master once until it is completed.
You can then run “./make.sh shell” which will drop you into a shell in the build environment. In there, you can run the gcc commands with the IPFire compiler, headers and use the entire rest of the user land.
You should not need any special search paths for any include files.
-Michael
> On 22 Dec 2024, at 02:25, jon <jon.murphy(a)ipfire.org> wrote:
>
> All,
>
> Is there a way to compile a C program and not run the entire ipfire `make.sh build`. And include the various ipfire `#include` items?
>
> I am attempting to compile an `rpzctrl.c` file for the `rpz.cgi` webgui. I am in the early stages of C programming and I am making lots of errors. And so each iteration of C code takes 2-3 hours for a `make.sh build`.
>
> I'd like to do something like:
>
> ```
> gcc -I ./build_x86_64/usr/include rpzctrl2.c -o rpzctrl
> ```
>
> I don't know which `include` files directory to reference so I just picked one. But running gcc throws lots of errors.
>
> Can you get me started?
>
> Merry Christmas all,
> Jon
>
>
prev parent reply other threads:[~2024-12-23 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 1:25 jon
2024-12-22 10:17 ` Matthias Fischer
2024-12-23 11:23 ` Michael Tremer [this message]
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=E7B09BE4-0F4D-433F-B16E-69775905CD2B@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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