public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Peter Wiehe <peter.wiehe2@gmail.com>
To: edk2-devel <edk2-devel@lists.01.org>
Subject: Re: Newbie: Getting Ovmf built
Date: Sat, 24 Nov 2018 18:23:59 +0100	[thread overview]
Message-ID: <CAJzXLLwXGjwvyx66P_sZT6-tRa+yeqd2GPi5cYYSyTCpaUfYEQ@mail.gmail.com> (raw)
In-Reply-To: <e6fbddcd-af70-793f-459b-9a9a3e3f09b3@linux.intel.com>

OK

Building went well to a certain point. I successfully git cloned. I
built the BaseTools.

I (seemingly successfully) setup the build shell environment. (I got no errors.)

In the target conf file I chose "IA32 X64" and ELFGCC (since I habe
gcc 7.3.0 installed).
When I type "build", there comes an error like "Command build not found".

I thought that maybe it's because of the shell environment variable
$PATH. $PATH does NOT contain the edk2 source directory in any way
(despite the fact that I entered "export EDK_TOOLS_PATH...").

What can I do?

Greetings
Peter

2018-11-24 1:40 GMT+01:00, stephano <stephano.cetola@linux.intel.com>:
> Hello Peter,
>
> Thanks for giving EDK2 a try!
>
> We have a set of simple instructions for folks building on standard
> Linux distros. Please have a look at this page:
>
> https://github.com/tianocore/tianocore.github.io/wiki/Common-instructions
>
> Note: Be sure the TARGET_ARCH is set correctly. (E.g. TARGET_ARCH = x64)
>
> Once you have built the BaseTools and MdeModulePkg without any errors,
> you can try building and running in OVMF:
>
> https://github.com/tianocore/tianocore.github.io/wiki/How-to-build-OVMF
>
> Tip: Add the -j option so that you can grep through the log easily for
> any errors (build -j /path/to/log/file.txt).
>
> Hopefully those links help get you started. Let me know if you run into
> any other issues.
>
> Cheers,
> Stephano
>
> Stephano Cetola
> TianoCore Community Manager
>
> On 11/23/2018 2:44 PM, Peter Wiehe wrote:
>> Hello, I'm a total newbie to Tianocore/EDK2/OVMF.
>> (My coding is at high school level I think, not university level. I
>> have some (small) experience writing in Assembler, C, C++. I wrote a
>> little bootloader, so I know something about filesystem in general and
>> ext2 and pre-kernel "environment".)
>>
>> I use xubuntu 18.04 on an AMD 64bit PC.
>>
>> I'm currently trying to
>> 1.) build OVMF from source
>> 2.) and then want to run it in/with Qemu.
>> 3.) Later I would like to try to write a simple ext2 "driver". Can't
>> guarantee I will succeed, but let's see.
>>
>> So far I have
>> 1.) downloaded the whole edk2 zip/tar-ball
>> 2.) have installed nasm and ASL (iasl)
>> 3.) Run "EmulatorPkg/build.sh"
>> 4.) Run "OvmfPkg/build.sh -a X64"
>> 5.) Run "OvmfPkg/build.sh -a X64 qemu"
>>
>> Then I get the error message "qemu-system-x86_64: -pflash
>> /home/peter/Schreibtisch/edk2-master/Build/OvmfX64/DEBUG_GCC5/QEMU/bios.bin:
>> Could not open
>> '/home/peter/Schreibtisch/edk2-master/Build/OvmfX64/DEBUG_GCC5/QEMU/bios.bin':
>> No such file or directory"
>>
>> So my first question is how to deal with this error.
>>
>> Kind regards
>> Peter Wiehe
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
>>
>


  reply	other threads:[~2018-11-24 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 22:44 Newbie: Getting Ovmf built Peter Wiehe
2018-11-24  0:40 ` stephano
2018-11-24 17:23   ` Peter Wiehe [this message]
2018-11-24 17:57     ` stephano
2018-11-24 18:03       ` Peter Wiehe
2018-11-24 19:45         ` Andrew Fish
2018-11-24 19:46           ` Peter Wiehe
2018-11-24 20:44             ` Andrew Fish
2018-11-26 14:09     ` Gao, Liming
2018-11-25  5:59   ` Rebecca Cran
  -- strict thread matches above, loose matches on Subject: below --
2018-11-24 21:18 Peter Wiehe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJzXLLwXGjwvyx66P_sZT6-tRa+yeqd2GPi5cYYSyTCpaUfYEQ@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox