3 ms·

Yeah but they're not always installed on the random SBC you might be configuring, or an old incompatible version might be installed. And then I have to dig thro

by cozzyd 6y ago

Yeah but they're not always installed on the random SBC you might be configuring, or an old incompatible version might be installed. And then I have to dig through the build system to figure out the right way to set prefix etc. cmake and meson should really have a way to output a configure script and Makefile...

junon 6y ago
> cmake and meson should really have a way to output a configure script and Makefile `cmake .. -GMakefile` not enough for you?
- cozzyd 6y ago
  I mean, for distribution, so that cmake is not required for a user to compile the project.
  - jcelerier 6y ago
    How is that gonna help on windows where there is no /bin/sh ?
    - cozzyd 6y ago
      Install cygwin or msys or WSL? Windows is unusuable otherwise :). anyway, the particular case here is something like an academic computing cluster, where you don't have administrator access, and you want to compile some package that will install into some place like $HOME/project/usr. The system has no meson or bazel or scons and only some older version of cmake that may not meet the claimed minimum requirement of the random package you want to compile. Or it's some SBC that you dare not upgrade the operating system on because you don't know if there is some breaking kernel change with some hardware interface. Sure, locally installing a new version of cmake or some other build system is not too hard, but it's certainly additional friction.
      - jcelerier 6y ago
        > Sure, locally installing a new version of cmake or some other build system is not too hard, but it's certainly additional friction. for cmake it's basically wget https://github.com/Kitware/CMake/releases/download/v3.20.0/cmake-3.20.0-linux-x86_64.tar.gz tar xaf cmake-3.20.0-linux-x86_64.tar.gz export PATH=$PWD/cmake-3.20.0/bin:$PATH definitely simpler than installing cygwin, msys or wsl :-) (and some software requires cl.exe on windows anyways)

by cozzyd 6y ago

junon 6y ago

> cmake and meson should really have a way to output a configure script and Makefile `cmake .. -GMakefile` not enough for you?

cozzyd 6y ago
I mean, for distribution, so that cmake is not required for a user to compile the project.
- jcelerier 6y ago
  How is that gonna help on windows where there is no /bin/sh ?
  - cozzyd 6y ago
    Install cygwin or msys or WSL? Windows is unusuable otherwise :). anyway, the particular case here is something like an academic computing cluster, where you don't have administrator access, and you want to compile some package that will install into some place like $HOME/project/usr. The system has no meson or bazel or scons and only some older version of cmake that may not meet the claimed minimum requirement of the random package you want to compile. Or it's some SBC that you dare not upgrade the operating system on because you don't know if there is some breaking kernel change with some hardware interface. Sure, locally installing a new version of cmake or some other build system is not too hard, but it's certainly additional friction.
    - jcelerier 6y ago
      > Sure, locally installing a new version of cmake or some other build system is not too hard, but it's certainly additional friction. for cmake it's basically wget https://github.com/Kitware/CMake/releases/download/v3.20.0/cmake-3.20.0-linux-x86_64.tar.gz tar xaf cmake-3.20.0-linux-x86_64.tar.gz export PATH=$PWD/cmake-3.20.0/bin:$PATH definitely simpler than installing cygwin, msys or wsl :-) (and some software requires cl.exe on windows anyways)