From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Mini build while experimenting with C programming? Date: Mon, 23 Dec 2024 12:23:38 +0100 Message-ID: In-Reply-To: <57FC3509-B2F7-4F9A-B83D-131180796AA7@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2647150324342723870==" List-Id: --===============2647150324342723870== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Jon, The easiest way to do this is to run the entire build from next or master onc= e until it is completed. You can then run =E2=80=9C./make.sh shell=E2=80=9D 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 wrote: >=20 > 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 --===============2647150324342723870==--