Alr.Commands.Build: forward subcommand args to gprbuild (#850)
* Update CLIC deps: Global switches are now only accepted before the subcommand
* Alr.Commands.Build: forward subcommand args to gprbuild
This will allow for instance:
$ alr build -f # force build
$ alr build -cargs -g # compile with an extra switch
$ alr build -f -u atomic.adb # only compile atomic.adb
This is exposing more of the gprbuild interface in an Alire workflow.
But I see this as a convenient development trick, and the standard "alr
build" command without extra args should always be enough to build a
crate.
https://github.com/alire-project/alire/issues/698
* Alr.Commands.Clean: fix -X switch handling
The variable Alr.commands.Scenario was hidden by
Alr.Commands.Clean.Scenario.
Alr.Commands.Toolchain: tweak for multiple components and install dir (#822)
* Alr.Commands.Toolchain: tweak for multiple components and install dir
This patch adds support of multiple components and allow
--disable-assistant with all commands so that it is possible to
configure all the toolchain stuff in one command:
$ alr toolchain --select gnat_native gprbuild --disable-assistant
The patch also introduces a --install-dir switch to allow installation
in any directory. This can be useful for people willing to use the Alire
toolchain outside of an Alire workflow. It would be better if the root
dir of the archive (e.g. gprbuild_21.0.0_349f6f95) was skipped so that
all the tools would be available from <INSTALL_DIR>/bin/.
* tests: increase gnat_native version in fixture index and add more tests
* Alr.Commands.Toolchain: print list only when no command is specified
* tests/toolchain/custom_install_dir: fix paths for Windows and second dir
The goal of this big refactoring is to extract the handling of
sub-commands to make it available for other projects.
The SubCommander packages (name open to changes) can be extracted to a
dedicated crate or to AAA.
There is at least one regression which is the support of -X for alr
build.
* Alr.Commands.Toolchain: Fix comparison typo from refactoring
* Alr.Commands|SubCommander: Fix exception raise and handling
* Typo
* Address review comments and minor changes
* Another big refactoring on command line handling
The switches are not parsed several times like before. The global
switches parsing is done once, the command specific switch parsing is
done only on the command arguments.
Handling of -X scenario variable switches is now done with regular
GNAT.Command_Line switch handling.
There is a issue with command arguments that contain spaces, it looks
like they are split in multiple arguments. I don't know why.
* Fix args filtering
The concatenation of arguments and re-splitting with
GNAT.OS_Lib.Argument_String_To_List breaks when arguments have
whitespaces: 'alr' 'show' 'a b c' becomes 'alr 'show' 'a' 'b' 'c'.
* Wrap the GNAT Commnand_Line_Configuration to add required features
This was previously done with a GNAT.Command_Line.Extra package that
exploited the internals of GNAT.Command_Line.
This is more portable because less exposed to changes in the internals
of GNAT.Command_Line.
* Rename SubCommander to CLIC.Subcommander and move it to alire/
* Move Alire.Utils.User_Input and Alire.Utils.TTY to CLIC
Hide alr-deployed releases from external detection (#805)
This is done so when a regular compiler from Alire is put in the path, it won't
be doubly available as a regular release and as an external release, which may
be confusing.
Binary crates, toolchain management and use (#775)
* Implement sha256 and hash use test (#765)
* Implement binary origins and their deployment
* `alr install` for shared installations
Essentially, we have a second location for dependencies at ${ALR_CONFIG}/cache.
In following PRs the releases therein will be available during dependency
resolution, to be reused.
`alr install` for manual crate installation
Installed crates are used by the solver
Autodiscover installed releases
Show differences due to changed install status
Install: implement release removal
* Toolchain configuration assistant
Menu for choosing among multiple options
Show actual compiler versions to the user
Install and remember the user choice
User_Input: Take a possible Ctrl-D into account
* Re-enable "provides" in index and use them in alr
New, more flexible provides type
WIP: going back to provides as list of deps
All but loading of "provides"
Loading of provides
Installed provides are used during solving
They're not yet used for regular dependencies
Display provider in the `alr with` variants
Prevent solving of conflicting dependencies
If two releases provide the same crate, they cannot be simultaneously in a
solution.
solver tweaks for provides + externals
Improvements to solution space by reusing releases
When adding a release to a solution, check whether other dependencies can be
satisfied by this same release. Not a big deal, could be disabled if too costly
in the future.
* Use toolchain in solve/build/environment
Insert explicit dependency on the configured gnat
Do not explicitly insert dependency on toolchain
Instead, we simply coerce when given a generic gnat dependency into the
configured one. This is less intrusive as the user does not see unexpected
dependencies on the compiler in the solution (unless explicitly requested).
Extra info in `alr install` list
Generalized assistant for all tools in toolchain
* Rename install command to toolchain
* Implement "provides" for external detectors
For now this is restricted to a single alternate crate name. By necessity, the
equivalence has to be to the same version, whereas provides for regular
releases are more general as they can rely on precise versions which are known
in advance.
* Tweaks for new GNAT crate names
* Solver: reuse known GNAT on generic gnat= dep
* Integrate external gnats in shared releases
This is logical because these are always available in all configurations. But
the important benefit is that the solver can use them in preference to a remote
native compiler.
* Documentation in doc/, `alr help`
* Fixed circularity, Config.Edit is now untangled
* Tweaks to pass existing tests
* Self-review fixes and clean-up
* New tests for toolchains and related features
* Windows-specific testsuite fixes
* Review fixes
In particular, the avoidance of downloading a compiler for a generic gnat
dependency. This is tested in testsuite/tests/solver/compiler-installed
Fabien Chouteau [Tue, 3 Aug 2021 15:39:38 +0000 (17:39 +0200)]
Alr.Commands.Init: change defaults for init project to release mode (#777)
I first decided to make the default better for developers (to catch as many errors as possible), but they end up in release crates which means that the performance is bad as well as the compatibility between compiler versions.
This patch set the defaults to max performance and compatibility.
This system is clearly not very user friendly, maybe we have too many options here.
Profiles like in Cargo could be better.
Deploy dependencies atomically and related cleanup subcommand (#768)
* Use a temporary to fetch & deploy releases
This is done to avoid an interrupted download (for example with Ctrl-C) to
mistake our deployer, which considers an existing directory as a successfully
deployed dependency.
* Cmd.Clean: implement --temp option
To remove any dangling temporaries
* Improve clean --cache to avoid useless downloads
Fix corner case when pinning to a not available version (#767)
* Less confusing user feedback for existing pin
* Typo in comment
* Fix for corner case in which no solution was found
The solution is impossible, but still an incomplete solution should be
returned. In essence, when the user requested an impossible situation by
applying a pin to a non-existent version for a crate already in the
dependencies, the solver reused the old version assuming it would succeed,
which was not the case if the pin is impossible.
* Better pin info separation
* Extra test case for pinning to unavailable version
projects / alire.git / log