feat: cc builder #22
No reviewers
Labels
No labels
Compat
Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: auxolotl/labs#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "vlinkz/labs:vlinkz/ccbuilder"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Basic gcc builder. Not yet fully featured, but enough to start.
Picked out of #21, example usage:
3e80b2e12e/tidepool/src/packages/core/hello/versions/2.12.nix.974dbc4b85to139750a59e139750a59etodc8f97c133@ -0,0 +85,4 @@configureFlags = builtins.concatStringsSep " " (lib.lists.when (settings.configure.prefix) [ "--prefix=$out" ]++lib.lists.when (settings.configure.platforms && package.platform.build != package.platform.host)Is there a reason why this shouldn't just be passed by default?
I think it's useful to disable these args if the configure script is
cmakeinstead, which does not support this form of arguments. But I'm not sure whether this specific builder would be the preferred way of working with CMake.These flags definitely should not be passed to CMake, should have its own attribute because the way it handles things are very different with types and such.
I was thinking we make seperate capabilities for cmake, meson, autotools, etc. Thoughts?
@ -0,0 +93,4 @@++lib.lists.when (settings.configure.platforms && package.platform.host != package.platform.target)["--target=${(lib.systems.withBuildInfo package.platform.target).triple}"Same with this.
@ -0,0 +95,4 @@["--target=${(lib.systems.withBuildInfo package.platform.target).triple}"]++ settings.configure.flagsThere are some other flags to be pass if it is an autotools-compatible configure script. Should we assume that? Examples:
--disable-static(and----enable-staticfor a static platform)--prefixView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.