cbpporter wrote on Thu, 11 January 2018 09:46

So fast!

I'll check!

Do you have idea on the other problem I mentioned? I can't debug even command line apps with "target file override".

Unable to reproduce (so far). "works on my machine"

Any further input on this is appreciated.

For now I had to revert versions.

I tried 2017.1 and it works, but it is way too ancient. It misses several fixes I need, 2 of them done by me. So I can't use it.

I am now on the 2017.2 RC, it has all the fixes I need and it works I think. Need to test more.

So from RC to release the debugging + target override got broken.

Narrowing it down further...

My tests were with a self-compiled TheIDE, but I was using a 64bit to debug 32, like I usually do. Updating to nightly didn't help.

But I figured that my upp folder was compromised and indeed, after a fresh install, it works. As an added bonus BLITZ works again. It didn't on my broken setup. Autodection works too, at least for 2017.

So everything is a go. Thank you!

Which reminds me: it is probably time to stop using 32 bit for good.

How do you manage both 32 and 64 bit binary releases? Not for U++, but in general. Two packages? One package with both 32 bit and 64 binaries, with different names? Is there some lightweight .bat or .exe or something to autodetect and launch the proper version?

But I figured that my upp folder was compromised and indeed, after a fresh install, it works. As an added bonus BLITZ works again. It didn't on my broken setup. Autodection works too, at least for 2017.

(Asking because thinking about doing the next release soon)

cbpporter wrote on Mon, 15 January 2018 10:37

But I figured that my upp folder was compromised and indeed, after a fresh install, it works. As an added bonus BLITZ works again. It didn't on my broken setup. Autodection works too, at least for 2017.

OK, so nightly build install now works out of box? (Asking because thinking about doing the next release soon).

Mirek