Lines Matching +full:libceed +full:- +full:sys
5 In preparing a release, create a branch to hold pre-release commits.
21 Use `git log --first-parent v0.7..` to get a sense of the pull requests that have been merged and t…
22 …ences for key features to highlight on [GitHub releases](https://github.com/CEED/libCEED/releases).
25 Use `make doc-latexpdf` to build a PDF users manual and inspect it for missing references or format…
31 … compliance checker](https://github.com/lvc/abi-compliance-checker) is a useful tool, as is `nm -D…
33 …cised in continuous integration (e.g., HPC facilities) and with users of libCEED, such as MFEM and…
34 … PR to support the new release, and it's good for quality to test before tagging a libCEED release.
38 4. Check that `spack install libceed@develop` works prior to tagging.
39 The Spack `libceed/package.py` file should be updated immediately after tagging a release.
44 1. `git commit -am'libCEED 0.8.1'`
45 More frequently, this is amending the commit message on an in-progress commit, after rebasing if ap…
47 3. `git switch main && git merge --ff-only HEAD@{1}` fast-forward merge into `main`
48 4. `git tag --sign -m'libCEED 0.8.1'`
50 6. Draft a [new release on GitHub](https://github.com/CEED/libCEED/releases), using a few sentences…
56 Generate the PDF using `make doc-latexpdf`, click "New version" on the [Zenodo record](https://zeno…
62 libCEED's Julia interface (LibCEED.jl) has two components:
64 * LibCEED.jl, the user-facing package that contains the Julia interface.
65 …wrapper package ("jll package") that contains prebuilt binaries of the libCEED library for vario…
67 When there is a new release of libCEED, both of these components need to be updated.
68 First, libCEED_jll is updated, and then LibCEED.jl.
73 In this PR, the file `L/libCEED/build_tarballs.jl` should be changed to update version number and c…
75 diff --git a/L/libCEED/build_tarballs.jl b/L/libCEED/build_tarballs.jl
76 --- a/L/libCEED/build_tarballs.jl
77 +++ b/L/libCEED/build_tarballs.jl
78 @@ -3,11 +3,11 @@
81 name = "libCEED"
82 -version = v"0.7.0"
87 - GitSource("https://github.com/CEED/libCEED.git", "06988bf74cc6ac18eacafe7930f080803395ba29")
88 + GitSource("https://github.com/CEED/libCEED.git", "e8f234590eddcce2220edb1d6e979af7a3c35f82")
91 …sion of libCEED_jll will automatically be registered, and then we can proceed to update LibCEED.jl.
93 ### Updating LibCEED.jl
95 …r package libCEED_jll has been updated, we are ready to update the main Julia interface LibCEED.jl.
96 This requires updating the file `julia/LibCEED.jl/Project.toml` in the libCEED repository.
99 diff --git a/julia/LibCEED.jl/Project.toml b/julia/LibCEED.jl/Project.toml
100 --- a/julia/LibCEED.jl/Project.toml
101 +++ b/julia/LibCEED.jl/Project.toml
102 @@ -1,7 +1,7 @@
103 name = "LibCEED"
104 uuid = "2cd74e05-b976-4426-91fa-5f1011f8952b"
105 -version = "0.1.0"
109 CEnum = "fa961155-64e5-5f13-b03f-caf6b980ea82"
110 @@ -26,4 +26,4 @@ Cassette = "0.3"
114 -libCEED_jll = "0.7"
120 $ cd julia/LibCEED.jl/gen
121 $ julia --project=../../.. -e 'include("generator.jl"); generate_ceed_bindings("../../..")'
123 Once this change is merged into libCEED's `main` branch, the updated package version can be registe…
125 > @JuliaRegistrator register branch=main subdir=julia/LibCEED.jl
131 LibCEED.jl has both _development_ and _release_ unit tests.
132 The _release_ tests are run both with the current build of libCEED, and with the most recent releas…
133 …t available in the most recent release, and so they are only run with the current build of libCEED.
136 …tests are found in the file `julia/LibCEED.jl/test/runtests.jl` and the development tests are foun…
142 …t has the `release preparation` label. One can also use `cibuildwheel --only cp310-manylinux_x86_6…
150 $ twine upload --repository testpypi wheelhouse/libceed-0.8-cp39-cp39-manylinux2010_x86_64.whl
154 $ pip install --index-url https://test.pypi.org/simple --extra-index-url https://pypi.org/simple li…
156 The `--extra-index-url` argument allows dependencies like `cffi` and `numpy` from being fetched fro…
159 $ twine upload --repository pypi wheelhouse/libceed-0.8-cp39-cp39-manylinux2010_x86_64.whl
165 The Rust crates for libCEED are split into
166 1. [`libceed-sys`](https://crates.io/crates/libceed-sys), which handles building/finding the `libce…
167 2. [`libceed`](https://crates.io/crates/libceed) containing the safe and idiomatic Rust bindings.
173 $ cargo release --no-tag --no-push --no-publish 0.12.0 --execute
178 1. `cargo package --list --package libceed-sys` and `--package libceed` to see that the file list m…
180 3. `cargo release publish --execute` to publish the crates to https://crates.io