This is an older one, so the Xojo version is the one that was current at this day. I do not checked lately if this still happens.
I got consistently these error messages at stand alone application time. After some attemps, I created that screen shot and I forgot to report them (how / where ?).
I was not sure of what to do. Since this screen shot was done on 2013-12-16, I do not recall the details excepted that I got this message every time I wanted to create the stand alone.
I created them on OS X instead, when needed, since then.
Well, suppose you should check with the latest version to see if you still have a problem. And seeing as XP is no longer supported by Xojo I would maybe look to a newer version of Windows whatever happens here?
I wouldn’t expect Xojo to devote any resource to this if it turns out it’s still an issue and it’s XP related.
Due to the license price and the entry level hardware (and my Pentium IV laptop power supply is no more working), a brand new hardware have to be brough.
I get this “all the time” (that is, quite frequently) on Mac. The programs DEFINITELY 100% aren’t running. This is a Xojo “bug” - they need to try harder in deleting existing files.
I’ve assumed that Xojo gets some type of error trying to delete the existing files to replace and just throws this up there and gives up prematurely without trying all options.
I get this SO MUCH with no pattern nor apps running/shared etc. so it’s not on the users end, it’s a Xojo thing.
Xojo really needs to address this, it’s their issue, but in the meantime just make sure you aren’t overwriting anything. I find this a hard habit to invoke, but I have less/zero problems when I do it.
I completely understand, in my programs I try to delete files and I’ll get that. But in those cases AFAIK there’s a reason - I’ve opened the file, done something. And it happens more often in Windows.
But I’m doing Mac, and these are applications, whose only claim to the system is whether they are running or not.
Plus, I can easily delete the apps in the Finder without any complaint.
I am just saying that there IS a way to delete these things and Xojo just needs to be more brutal about it and not error so quickly. At least that’s my outside perception.
When you are compiling, (forgive me if I’m wrong) it’s only a single object on Mac, and an .exe and like-named folder with an added " Libs" added. So you always know which files they are.
I usually see it when I’m debugging, not just building. When I go to look, there’s nothing left over in my project folder that looks wrong…it’s going into a temp folder somewhere and I’m not sure where it is. It also happens sometimes when I open a new project to test something out and I don’t save the project. After a few runs, I sometimes get the error but have no idea what file(s) it’s talking about.
In debugging, on Win, Xojo constructs a folder called ‘[appname] Debug’ and inside that writes [appname].exe and a folder called ‘[appname] Libs’. AFAIK there’s nothing else going on, no temp folder stuff.
Persoanlly, I do some cheating and I write files into those locations to simulate the actual environment. In the REAL days, it didn’t create the ‘DEBUG’ folder, it just wrote ‘Debug[appname].exe’ in the same folder as the project (putting aside the “use builds folder” option).
Of course, I know the location of MY files. AS I recall, the error DOES NOT leads to the original project file (as far as I can recall).
Hey, Bill, you may be right. Where is that temp folder ?
Garth: I usually uncheck the “use builds folder” option.
And, since the project is a copy (Windows) of the real one (on OS X), I do not care to save changes (at one location/one time, if it works, I report the changes in the OS X project). That copy project is in the Shared folder of VirtualBox. I trash it when I do not need it anymore (or try to do that).
Embarrassingly enough, I was looking through the preferences for something else and found the location of the “unsaved apps build folder” in that. Xojo Preferences-Building-Build Unsaved Apps In.
Even more embarrassingly, I’d set it to something specific which means I’ve found it in the past and forgotten it since. sigh
No later than yesterday, it seems that I forgot to send two attached files (one for each target person). But in this case I have doubts on the error: I think it can be not mine )
When you do IF the compiler creates file that clobbers one of yours its not a bug
The builds folder is similar since if you compiled for Carbon & Cocoa (say using a build script to do this) those two builds would overwrite each other
We didn’t put this in there just to annoy people - really
