about summary refs log tree commit diff
path: root/pkgs/development/interpreters/cling
AgeCommit message (Collapse)AuthorFilesLines
2023-08-19cling: tidy/simplify + add experimental libc++ support (#247253)Tom McLaughlin1-34/+67
2023-05-09Disable jupyter kernel installation on darwinTom McLaughlin1-1/+1
2023-04-18Include the Jupyter kernel in $out/share/jupyterTom McLaughlin1-0/+5
2023-04-16Force installation of ClingTargets.cmakethomasjm2-0/+18
2023-04-16Patch cling/tools/driver/CMakeLists.txt, it works now!Tom McLaughlin2-1/+27
2023-04-15Take only the include dir from llvmPackages_9.llvm.devTom McLaughlin1-1/+2
2023-04-15Remove notes and fix clang include in flagsTom McLaughlin1-7/+7
2023-04-15Able to build cling 0.9Tom McLaughlin3-51/+46
2023-04-04More on cling patchTom McLaughlin1-18/+16
2023-04-04Tweaking LLVM patchTom McLaughlin1-5/+5
2023-04-04Bringing over more patchesTom McLaughlin2-4/+54
2023-04-04First clang patchTom McLaughlin2-0/+21
2023-04-04Working on update to cling 0.9Tom McLaughlin1-14/+14
2022-08-14cling: use makeWrapper for build platformRick van Schijndel1-1/+1
2021-08-15treewide: runCommandNoCC -> runCommandRobert Hensing1-2/+1
This has been synonymous for ~5y.
2021-05-08cling: fix llvm buildJonathan Ringer1-2/+3
2021-04-30llvmPackages: Multuple outputs for everythtingAndrew Childs1-2/+2
Also begin to start work on cross compilation, though that will have to be finished later. The patches are based on the first version of https://reviews.llvm.org/D99484. It's very annoying to do the back-porting but the review has uncovered nothing super major so I'm fine sticking with what I've got. Beyond making the outputs work, I also strove to re-sync the packages, as they have been drifting pointlessly apart for some time. ---- Other misc notes, highly incomplete - lvm-config-native and llvm-config are put in `dev` because they are tools just for build time. - Clang no longer has an lld dep. That was introduced in db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help finding lld when it is used we should just pass it flags / put in the resource dir. Providing it at build time increases critical path length for no good reason. ---- A note on `nativeCC`: `stdenv` takes tools from the previous stage, so: 1. `pkgsBuildBuild`: `(?1, x, x)` 2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)` while: 1. `pkgsBuildBuild`: `(?1, x, x)` 2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)` 3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2021-03-25cling: use python3Frederik Rietdijk1-2/+4
2021-01-23pkgs/development/interpreters: stdenv.lib -> libBen Siraphob1-3/+3
2020-12-21cling: fix libc include path for non-glibcDmitry Kalinkin1-1/+1
2020-11-19cling: init at 0.7.0 (#64319)Tom McLaughlin1-0/+102
Co-authored-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>