Skip to content
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

Fix support for MinnowBoard Turbot #9

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

pietrushnic
Copy link
Member

Signed-off-by: Piotr Król [email protected]

@@ -1 +1 @@
1.2.1
vUDK2017
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume we are starting with the very first tag of EDK2 and will gradually add support for newer versions? vUDK2017 is so old...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@miczyg1 no, this would be economically not feasible. We adding what is needed, not necessarily in chronological order: https://github.com/3mdeb/edk2-docker/pull/9/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R9


[ ! -d edk2/CryptoPkg/Library/OpensslLib/openssl ] && git clone -b OpenSSL_1_1_0e https://github.com/openssl/openssl edk2/CryptoPkg/Library/OpensslLib/openssl

docker run --rm -it -w /home/edk2 -v $PWD/scripts:/home/edk2/scripts -v $PWD/edk2:/home/edk2/edk2 -v $PWD/edk2-platforms:/home/edk2/edk2-platforms -v $PWD/minnowboard_max-1.01-binary.objects:/home/edk2/silicon -v ${CCACHE_DIR:-$HOME/.ccache}:/home/edk2/.ccache 3mdeb/edk2:vUDK2017 bash /home/edk2/scripts/build_minnow.sh
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This command asks for line breaks. Can we use \ to divide it into more lines for better readability?

@macpijan
Copy link
Member

@miczyg1 @pietrushnic any ideas what we should do with this PR?

@pietrushnic
Copy link
Member Author

I guess we should address all discussions and merge. Of course this repo no longer make sense since there are upstream containers which we should rely on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants