-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation desired on Linux build system requirements #381
Comments
Adding @@ -8 +8 @@ RUN apt-get install -y git wget xz-utils
-RUN apt-get install -y make cmake ninja-build
+RUN apt-get install -y build-essential make cmake ninja-build
@@ -15,2 +14,0 @@ RUN tar --no-same-owner -C ${SDK_INSTALL_PREFIX} -xJf llvm-mos-linux.tar.xz
-ENV PATH=${SDK_INSTALL_PREFIX}/llvm-mos/bin:${PATH}
-
@@ -22,0 +21,2 @@ WORKDIR /tmp
+
+ENV PATH=${SDK_INSTALL_PREFIX}/llvm-mos/bin:${PATH} I haven't checked the minimal set of dependencies (e.g. Perhaps the Development procedure could be updated, so that it mentions more dependencies? |
I don't see in our documentation where we teach coders how to set up a development system. I'm not sure that information belongs in the SDK, though I am willing to listen to argument regarding this point. |
Generally agree w @johnwbyrd. If we had detailed steps about how to set up a build environment on e.g. Debian, then from what I've seen it's customary to include |
I don't know how MOS llvm is organized in details. Reading Development procedure I assumed that MOS llvm / SDK is somehow self-sufficient to build itself. Now I know, that I need My idea was to add maybe a simple tip to the documentation (a few words like above and platform agnostic) so that others can avoid the trap I fell into. I fully agree that it's not the place to teach how to setup a C/C++ environment nor to explain how it can differ between possible platforms. BTW, in case of Ubuntu |
I'm trying to apply a patch to SDK.
However, when I follow Development procedure I get an error.
What can be wrong?
The procedure (as Dockerfile):
The procedure fails in
cmake
step:Relates to: #378 issue, 4fc7b2d patch.
The text was updated successfully, but these errors were encountered: