[Hackrf-dev] Is there a simple step-by-step guide to building the hackrf firmware?

[Tony Naggs]

On 3 October 2013 17:41, Dominic Spill <dominicgs at gmail.com> wrote:

>

> I only worked this out for myself last week, so there could be subtleties that I'm missing.


Thanks for the prompt reply. It feels better than I'm not lagging
behind everyone as much as I thought.


> Is libopencm3 in hackrf/firmware/libopencm3?


Not currently, but I had the same issues when I tried building it there.


> You can use git's submodule features to get libopencm3 in the correct place or just clone/move it to the right place.


Okay, thanks. I have been avoiding git up to now - I quite like svn or hg.


> > For libopencm3 I can't see how to just build for lpc43xx, so just 'make'.

>

> If libopencm3 is in the firmware directory, then you can skip the step of building the library separately and go straight to building the firmware that you need.


I have wiped the files and setup like that, but it is no better:
  BUILD   blinky
dirname: extra operand `Files'
Try `dirname --help' for more information.
make[1]: Entering directory `/home/tonyn/projects/hackrf/firmware/blinky'
c:/program files (x86)/gnu tools arm embedded/4.7
2013q3/bin/../lib/gcc/arm-none-eabi/4.7.4/../../../../arm-none-eabi/bin/ld.exe:
cannot open linker script file libopencm3_lpc43xx.ld: No such file or
directory
collect2.exe: error: ld returned 1 exit status



> Let me know if you have any more questions that I might be able to help with,


It seems like the issues may be with working in Cygwin, I guess I will
try creating & using a Linux VM. :-/

Ttfn.