[Solved] Weird BDIR path


#1

Hi folks,
I've dusted off my Axoloti after a year for a play and found I can't compile patches anymore. I seem to be getting a space tagged onto the BDIR path. Here's the error.

Axoloti version : 1.0.12-2-0-g7975cc87  build time : 09/04/2018 13:05:40 UTC
Link to firmware CRC E95BAC96
Status: factory (1.0.12,anon) : OK  ( 1.0.12,clean )
Status : home : OK
Status: community (1.0.12,anon) : OK  ( 1.0.12,clean )
USB device found
connected
Authentic Axoloti Core
search path : /home/mongrol/axoloti/axoloti-factory/objects
Firmware version: 1.0.0.1, crc=0xE95BAC96, entrypoint=0x20011000
search path : /home/mongrol/axoloti/objects
search path : /home/mongrol/axoloti/axoloti-contrib/objects
finished loading objects
Generate code complete
Start compiling patch
Compiling patch... with /opt/Axoloti/app/firmware
BDIR = /home/mongrol/axoloti/build\ 
FIRMWARE = .
make: *** No rule to make target '/home/mongrol/axoloti/build /xpatch.cpp', needed by '/home/mongrol/axoloti/build /xpatch.bin'.  Stop.
shell task failed, exit value: 2
Compiling patch failed ( untitled )

How is that path set? The build folder definitely doesn't have a space in it.


#2

Fixed. I installed V2 after blitzing my old install. All good.


#3

V2 is not recommended, there are a lot of bugs.


#4

Ah, erk... back I go then :slight_smile:


#5

In case you didn't already see it yet, there is this thread about 2.0:


#6

So I've reverted back to 1.1.12 and I'm back at the original problem.

USB device found
connected
Authentic Axoloti Core
Firmware version: 1.0.0.1, crc=0xE95BAC96, entrypoint=0x20011000
Generate code complete
Start compiling patch
Compiling patch... with /opt/Axoloti/app/firmware
BDIR = /home/mongrol/axoloti/build\ 
FIRMWARE = .
make: *** No rule to make target '/home/mongrol/axoloti/build /xpatch.cpp', needed by '/home/mongrol/axoloti/build /xpatch.bin'.  Stop.
shell task failed, exit value: 2
Compiling patch failed ( untitled )

With the space in the build path breaking the compile.


#7

Bug found and fix confirmed to work.


#8

Thank you for this patch. I had the same problem on Ubuntu 22.04, and changing those three lines fixed it.