Build issue: is there a shortcut?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Build issue: is there a shortcut?

Jörg F. Wittenberger
Hi all,

while cross compiling I wonder: this builds (in my case) a lot of
binaries which have a path compiled in into the development
environment.  These are essentially useless.  They just take my time to
compile and waste space on the SSD.

Probably there is a target for `make` to use instead of the default,
which would just build the (static) library and *.import.scm files I
need on the host system.  Just which one I haven't been able to figure
out.  Which one is it?

Thanks to much.

/Jörg

_______________________________________________
Chicken-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/chicken-users
Reply | Threaded
Open this post in threaded view
|

Re: Build issue: is there a shortcut?

felix.winkelmann
> Hi all,
>
> while cross compiling I wonder: this builds (in my case) a lot of
> binaries which have a path compiled in into the development
> environment.  These are essentially useless.  They just take my time to
> compile and waste space on the SSD.
>
> Probably there is a target for `make` to use instead of the default,
> which would just build the (static) library and *.import.scm files I
> need on the host system.  Just which one I haven't been able to figure
> out.  Which one is it?
>

"make libs" could work, but I haven't tried it. The import libraries
should be produced as a side effect from building the libraries, IIUC.


felix


_______________________________________________
Chicken-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/chicken-users