From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Mini build while experimenting with C programming?
Date: Sun, 22 Dec 2024 11:17:07 +0100
Message-ID: <24a74cc5-56d0-4697-bb69-b4c4afebda2d@ipfire.org>
In-Reply-To: <57FC3509-B2F7-4F9A-B83D-131180796AA7@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1883621124526881976=="
List-Id: <development.lists.ipfire.org>

--===============1883621124526881976==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Jon,

as far as I remember:

The compilation of these C-files is controlled by 'lfs/misc-progs'
(make.sh / Core 189 / line 1720) and logged in a file named something
like 'log_x86_64/misc-progs'.

To put it in a nutshell: it could be sufficient if you just delete this
specific log file and start 'make.sh build' again. The lack of this log
file will trigger a new compilation process of 'misc-progs'.

HTH,
Matthias

On 22.12.2024 02:25, jon wrote:
> All,
>=20
> Is there a way to compile a C program and not run the entire ipfire `make.s=
h build`.  And include the various ipfire `#include` items?
>=20
> 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`.
>=20
> I'd like to do something like:
>=20
> ```
> gcc -I ./build_x86_64/usr/include rpzctrl2.c -o rpzctrl
> ```
>=20
> I don't know which `include` files directory to reference so I just picked =
one.  But running gcc throws lots of errors.
>=20
> Can you get me started?
>=20
> Merry Christmas all, =20
> Jon
>=20
>=20


--===============1883621124526881976==--