It would be nice if ./scripts/build.sh had an option to ignore the GUI build.
I often run into cases where the GUI will not build due to version conflicts between exact versions of npm, yarn, node, and a host of other things. I don't use the GUI do it would be nice to have the option of only building the kelp binary.
e.g., in v1.12.0, the GUI fails to build for me, because it's trying to use node-gyp to build paltform-specific bindings a specific version of node-sass:
In file included from /home/davek/.node-gyp/16.13.0/include/node/v8.h:30,
from /home/davek/.node-gyp/16.13.0/include/node/node.h:63,
from ../../nan/nan.h:58,
from ../src/binding.cpp:1:
/home/davek/.node-gyp/16.13.0/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
/home/davek/.node-gyp/16.13.0/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
492 | !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
| ^~~~~~~~~~~
| remove_cv
I'm sure the root cause of the error is on my side, but it would be nice if I could just ignore the GUI build instead of tracking it down.
It would be nice if
./scripts/build.shhad an option to ignore the GUI build.I often run into cases where the GUI will not build due to version conflicts between exact versions of
npm,yarn,node, and a host of other things. I don't use the GUI do it would be nice to have the option of only building thekelpbinary.e.g., in
v1.12.0, the GUI fails to build for me, because it's trying to usenode-gypto build paltform-specific bindings a specific version ofnode-sass:I'm sure the root cause of the error is on my side, but it would be nice if I could just ignore the GUI build instead of tracking it down.