Where does makeboot.bat put the resulting .elf file?

[sparxfly]

Don-

Running makeboot.bat in Windows 10, but I can't find the resulting elf file anywhere!
Under Win7 it always put it in the zboot\obj folder.
Snip of batch file output is attached...

[sparxfly]

I can't find the resulting elf file anywhere!

Actually, I can't find any generated files from running makeboot.bat.
Appears to be something wrong with paths under Win10?
Running current version of all ZBasic utilities.

[dkinzer]

Appears to be something wrong with paths under Win10?

I don't have access to Windows 10 here. I'll do some research to see if others are having issues with gcc and related utilities under Windows10.

[dkinzer]

I installed Win10 in a VirtualBox, installed ZBasic and then ran makeboot.bat in the zboot subdirectory of the ZBasic installation directory. As I expected, the output files weren't anywhere to be found. As with previous versions of Windows as far back as Vista, the OS doesn't allow apps to write to files in directories like "Program Files". Rather, it places such files in a "virtual store". I can't seem to find the virtual store on Win10 but on Win7 it is /Users/<user-name>/AppData/Local/VirtualStore.

The best way to work around this issue is to build in some other directory. I copied the entire zboot directory to a new directory: /tmp. Running makeboot.bat there results in the .hex file for the bootloader being generated in the /tmp/zboot/boot subdirectory. The .elf file and other intermediate files are generated in a device-specific subdirectory of the obj subdirectory of the build directory - in my test case /tmp/zboot/obj/atmega644p.