Can't compile patch in Win 10 using 1.0.12

#1

I am running on Windows 10, 64-bit, with the latest updates on a quad-core AMD laptop.
JRE is version 8, rev 144.
No patches will compile. Here is the Axo command window:

Axoloti version : 1.0.12-0-g80370d2 build time : 02/02/2017 20:39:14 CET
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
not accesseable : -12
USB device found
connected
Authentic Axoloti Core
search path : C:\Users\Greg O'Drobinak\Documents\axoloti\axoloti-factory\objects
Firmware version: 1.0.0.1, crc=0xE95BAC96, entrypoint=0x20011000
search path : C:\Users\Greg O'Drobinak\Documents\axoloti\objects
search path : C:\Users\Greg O'Drobinak\Documents\axoloti\axoloti-contrib\objects
finished loading objects
Generate code complete
Start compiling patch
BDIR = C:\Users\GREGO'~1\DOCUME~1\axoloti/build
FIRMWARE = .
RM
rm: cannot remove C:\\Users\\GREGO~1\\DOCUME~1\\axoloti/build/xpatch.o C:\\Users\\GREGO~1\\DOCUME~1\\axoloti/build/xpatch.elf': Invalid argument
rm: cannot removeC:\Users\GREGO~1\DOCUME~1\axoloti/build/xpatch.bin C:\Users\GREGO~1\DOCUME~1\axoloti/build/xpatch.d': Invalid argument
rm: cannot remove `C:\Users\GREGO~1\DOCUME~1\axoloti/build/xpatch.map C:\Users\GREGO~1\DOCUME~1\axoloti/build/xpatch.lst': Invalid argument
make: *** [C:\Users\GREGO'~1\DOCUME~1\axoloti/build/xpatch.bin] Error 1
shell task failed, exit value: 1
Compiling patch failed ( C:\Users\Greg ODrobinak\Documents\axoloti\axoloti-factory\patches\tutorials\14_additive_inharmonic.axp )

There are only three files in the build directory:
xpatch.cpp
xpatch.h.d
xpatch.h.gch

Can you please give some recommendation as how to solve this?

Many thanks!

#2

Odd error.

Try deleting the build directory, and make sure you don't have any anti virus software causing issues.
( you can put an exclusion in for that one directory)

#3

Thanks for your reply!

I have already tried deleting the build directory, but it makes no difference.'
The laptop that has this issue is running the same version of Norton as my other Win 10 laptop and that one has no issues with Axoloti. Note that neither laptop's Norton flags anything during the compile, so I know that is not an issue.

Is there some way to get the app into a 'debug' mode' so that I can get a more verbose listing in the command window? Also, is there a batch file that contains the commands that takes the patch and compiles it? And where is the environment set up that everything references for the patch compile?

One more thing. I didn't realize at first that I already had 1.0.11 installed on this laptop, so I had both 1.0.11 and 1.0.12 installed when I first invoked 1.0.12. When it didn't compile, I un-installed both versions via the Windows control panel, then I re-installed 1.0.12 according to your instructions. But as you can see, no luck.

BTW,what does the "not accesseable : -12" mean in the listing I sent?
Thanks again!

#4

-12 , sounds like some kind of usb fault... probably device not ready, you shouldn't be getting this, sounds like some kind of (PC) hardware issue.. cable,hub, etc ... check you have power saving off on the usb.
anyway, not related to you compile issues, and looks like it 'finally connects', but perhaps when can compile it may or may not give issues...

debug - no real debug mode, but if you start Axoloti from the command line, you will see a whole load of more messages displayed

scripts, are in the app/firmware folder ... if you check them, you will see what environment vars they need , these are setup within the application.... I think though, they generally default correctly.
(I don't really use them on windows, or from a runtime image, but they are the same as the dev ones)
as you will see, the scripts really just set things up, at the core (unsurprisingly :wink:) we use Make to do the compilation.

Id also suggest you try to download and reinstall the axoloti_runtime, as this is the part that seems to be giving you problems.

(fyi, ive got a windows 10 laptop here, latest updates, 64 bit and its running absolutely fine)

#5

Thanks much, Mark!

Yeah, this laptop seems to maybe have some issues.
I will try once more with dloading the runtime, then try the command line trick.

Have a great one,
Gregory