hmm, i’ve tried to use the VC++ toolkit 2003 but i’ve not a buggering clue how to set the flags so that it actually works…
someone HAS replied finally to the thread on the MSDN forum, but they say they can’t help without more info. i can’t give any, really…
also, the jucedemo.exe build on your site is from a different version of juce and i don’t know which… (notable difference- the popup menus default to the nicer big size when compiled lately) and comparing the dependencies of my build and yours shows it to be just a bit too different. also, if i try to upx any of my older builds, i get no luck there either (go figure)
any chance you (jules) can knock together a build that works and one that you’re not so happy with with the new VC++e?
Cheers, hadxyn - I can do a build that doesn’t work, but not an old one, because to install the latest version of VCX it forces you to uninstall the old one, and foolishly I’ve not kept a copy of the old installer.
I’ve also not seen it run on a win2k machine myself, but apparently it just completely fails to start - the hourglass cursor shows for a second, but nothing appears in the task manager.
I imagine MS’s response would be “just install the .net runtime on the win2k machine”…
i tried to UPX the output binaries from my latest builds, and i get that error. i then thought i’d try to do a upx compression on some of my older projects (such as when i started using juce) - they were most definitely build on the older release. what do you know - they don’t upx either, and using the --force command creates apps that don’t start.
also, i’ve had a couple of people contact me regarding my plugins, and that they don’t work on their system (usually it doesn’t appear, or just doesn’t have any kind of gui at all) - invariably it comes down to them having windows 98.
perhaps it is not just a difference between the beta and the release? i’ve never had any other version on this system - only ever VC++express - whereas i take it you have VC6 also? perhaps that is more where the ‘problem gradient’ starts from…
i really wish i had a clue about how to get the VC2003 toolkit compiler working, then at least i’d have a shot at trying out some more ideas. it just gives me some really odd errors!
well, i’ve managed to get someone to at least try some stuff out now, but i feel i’m not really getting anywhere. perhaps the people who made upx may be able to tell if there’s actually something wrong with the headers (which could be directly linked to the platform compatibility issue) or if it’s just picking up something perfectly valid that it just hasn’t been programmed to spot.
Well at least the guy on the forum said he had it working there, but could that be because they’ve got the .net toolkit installed on their win2k machines?..
mysterious! sorry i got the wrong end of the stick about the upx thing, but now i’m baffled as to why i can’t get it to compress ANY of my binaries… what the heck could be different about my system that makes it produce uncompressable binaries? perhaps it’s because i have an athlon? or perhaps it’s because … well, i can’t think of any reasons!
part of me thought “perhaps it’s since trying to use the latest platform SDK” but nope, all my old stuff (using the same SDK you use) is the same.
It’s very strange. And I can compress things but they don’t work.
I just posted again on the MS forum, because I messed with some settings (I think it was something to do with whole-program or link-time optimisation) and got my builds to work on win2k/98, though I don’t know exactly why. But they still don’t compress with UPX.
I believe I’m now in exactly the same spot as you! :hihi:
I got an email back from one of the UPX devs, and he suggested that I set the linker flag /SAFESEH:NO - this got rid of the warning for me for both beta and stable versions of UPX, so they compress without qualm now… but now I just get that Runtime error.
laszlo (upx) has been having a look at what the problem might be, and has just emailed me back a successfully upx’d (and runnable) version of an un-upx-able exe i sent him. i think that means that he may well have sussed it out and have a new version of upx for us…
[quote=“Laszlo”] The fix was simple, I’ve made a copy of
the original data, and put it into the compressed file (uncompressed).
My patch is not complete yet, as it would not work will .dlls. I’ll
check it into the cvs soon. When Markus releases a new beta you could
try it.
[/quote]
Not quite sure what he means exactly :oops: :hihi: but hopefully the next version should work for us. I’ll keep an eye on it.
i tried downloading the 1.9x beta of upx, and now the error i get is:
“Structured Exception Handling present (try --strip-loadconf)”
Did you try compiling with /EHsc instead of /EHa (which I think the Juce project use)? – it’s in C/C++ // Code Generation // Enable C++ Exceptions. No idea if that would solve anything but that should remove the structured exception handling from your binary…
Hopefully without disrupting this conversation to any great extent, may I ask whether you’re still planning on making that “all-in-one starter pack” that you were considering, hadyxn? I’m trying to see if what I’ve been working on in Linux will work on Windows, but I’m rather slow with these things, and from the sound of what you’re saying about the windows executable stuff and the MIA files I doubt I would be able to get this stuff set up just by my own sleuthing.
If you are still working on it/are planning to work on it, then I appreciate it very much such helpful people and the kits/tutorials they make make coding accessable to every newbie all over the world!
for exe compression PECompact is working fine for me. free for non-commercial. it’s got a GUI too, but it fitted right into my release build in VS express.
such helpful people and the kits/tutorials they make make coding accessable to every newbie all over the world!