cos7 CDTs and new compilers
See original GitHub issueAs part of our effort to add support for cos7 to linux-64, we’d like to do some refactoring of the structure of our CDTs. We (@isuruf and myself) are looking for community help in this work.
To do:
- make sure old CDTs are mutually exclusive with the new ones
- patch the repo data to make all current CDTs conflict with the sysroot packages (https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/60)
- patch the CDT repo data on defaults so they conflict with the sysroot package (https://github.com/AnacondaRecipes/repodata-hotfixes/pull/94)
- patch repodata so that new sysroots don’t interact with old compilers (https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/66, https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/65)
- build CDTS
- setup one-off CDT builds on conda-forge (https://github.com/conda-forge/cdt-builds/pull/2)
- build all of the old-style CDTs
- build all of the new-style ones too
- make all CDTs use
no_hoist: true
in the source sections - new-style CDTs should use the new
conda
sysroot (i.e.,{{ arch }}-conda-linux-gnu
) sysroot - new-style CDTs should depend on the correct version of the sysroot package (i.e., cos6 depends on 2.12 and cos7 depends on 2.17)
- old-style CDTs need to have the proper run_constrained
- see https://hackmd.io/T5q0GPa1QfKfQ6irNWAe5Q?edit for notes from the CDT discussion
- move to only conda-forge CDTs
- enable strict channel priority in the ci setup scripts (to make sure we always use our CDTs, https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/110)
- turn on new compilers
- finally remove the symlinks and CDT-location variants in the new compilers (https://github.com/conda-forge/linux-sysroot-feedstock/pull/26, https://github.com/conda-forge/linux-sysroot-feedstock/pull/27)
- make sure to add a sysroot run dep to
gcc_impl
,gxx_impl
andgfortran_impl
so that the repo data patches above don’t break the new compilers (https://github.com/conda-forge/ctng-compilers-feedstock/pull/32)
cc @isuruf @jakirkham @kkraus14 @nehaljwani @mingwandroid @jjhelmus
xref: https://github.com/conda-forge/conda-forge.github.io/issues/900 closes https://github.com/conda-forge/ctng-compilers-feedstock/issues/28
Issue Analytics
- State:
- Created 3 years ago
- Comments:19 (18 by maintainers)
Top Results From Across the Web
2020-07-01 conda-forge core meeting
2.17 for cos7. old plan is to roughly. patch repo data to make current CDTs on conda-forge conflict w/ new compilers (PR issued)....
Read more >How to install and use Eclipse CDT for C/C++ programming
Launch Eclipse ⇒ Help ⇒ Install New Software ⇒ In "Work with" field, pull down the drop-down ... CDT searches the PATH to...
Read more >C / C++ IDE (CDT) » Adding new "toolchain" to Eclipse.
works to compile C or C++ code on my Pi Zero with Raspian Jessie. Interestingly, the gcc compiler in the same place did...
Read more >Adding compiler switch to Eclipse CDT Built ... - Stack Overflow
On the same preference page, if you switch to the Providers tab (rather than Entries ), and select the CDT GCC Built-in Compiler...
Read more >Intel® Fortran Compiler
Microsoft Visual Studio* (Windows only); Eclipse* C/C++ Development Tooling (CDT, Linux only); Xcode (macOS and Intel Fortran Compiler Classic only) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I planned to do this at the core meeting
I will push the script later. There are ~250 cdts in defaults. Idk which ones we use