June 8, 2012 at 10:06 am #1156
Well if you have VC++, run it, start Glade and attach the debugger to the process. Then send me the stack trace when it crashes.March 7, 2013 at 4:22 pm #1336
One important point – if you have problems getting glade to run on Windows, check if you have python27.dll installed in either of
If you're running a 64 bit version of Windows, the one in system32 should be the 64 bit one (this may not seem intuitive but then this is is Microsoft…) and the one in sysWOW64 should be the 32 bit dll.
Better still just use the ones in the default installations and start Glade from that directory.
If you're not sure, try using Dependency Walker (http://www.dependencywalker.com/) which will show you just which DLL's your executable is using and whether there are any conflicts.May 8, 2013 at 12:25 pm #1356
I am totally unable to run Glade on both Windows7 and WindowsXP.
Inspecting the *.exe with DependencyWalker I found that are a lot of missing DLLs.
I guess it is caused by missing dependencies.
Obviously the log file is empty.
Please, give me some hints.
Below the list of missing DLLs:
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLLMay 8, 2013 at 12:41 pm #1357
A quick google of 'API-MS-WIN-CORE-COM-L1-1-0.DLL' would indicate that you are missing some Windows DLLs. You might want to run Windows Update to check you have all the latest files.May 8, 2013 at 12:48 pm #1358
Trust me, both my Windows are highly updated.
I've done the same searches on Google.
If I am posting it is because I am not able to solve the problem by myself.
Is there any software that is "strongly recommended" to install before trying launching Glade?
(I can't stand the empty log file!)
Thank you so much…May 8, 2013 at 1:01 pm #1359
Normally you just have to install the runtime libraries, the Microsoft installer for these is provided in the distribution.
The DLLs you mention are not those however, they are core Windows API DLLs.
Are you running the 32 or 64 bit version?May 8, 2013 at 1:06 pm #1360
They are both 32bit systems.
I am interested in solving the issue on Windows7 seen that it is newer PC.May 8, 2013 at 2:20 pm #1361
Glade is built on a PC running Windows 7 – so I'll take a look and see if I have those DLLs on my machine. Will probably not be able to until later today though.May 8, 2013 at 6:28 pm #1362
OK, taking a look at the glade.exe built on my machine running Windows 7 (64 bit) with dependency walker, I also get a lot of missing DLLs (API-MS-WIN-*). There is some info on these DLLs here: http://www.nirsoft.net/articles/windows_7_kernel_architecture_changes.html
However, Glade runs just fine without them, as neither it nor the Qt libs call any functions from these DLLs. Dependency Walker doesn't know this alas, so it 'thinks' that it is a problem that they are missing.
I think these 'missing DLL' issues are a red herring, and your problem is that described in post #16 in this thread – i.e. you've got an incorrect python27.dll somewhere on your machine and are not using the python27.dll shipped in the installation directory. Look at which python27.dll you are picking up in dependency walker, and from where. If it's not from your Glade installation directory, then it's probably not the one you want…May 8, 2013 at 7:26 pm #1363
I am sorry but it's not working yet.
Python27.dll is the correct one.
Sorry for let you lose time.
I am attaching the dwi file from dependencywalker if it can help.
I will try with a Linux distro.
Thank you.May 9, 2013 at 7:21 am #1364
Couple of things that might help debug your windows problem:
1) If there is a missing DLL *that is required*, the program won't start and Windows will pop up a dialog telling you this. So that enables you to tell whether there are any missign DLL's.
2) When Glade starts, the first thing it does after setting up the logfile is to initialise Python using Py_Initialize. If Python fails to initialise, it will exit with no warning.
3) After that, the app window should show itself and messages will start to be written to the logfile. Do you see the app window, even briefly?
4) It may be worth trying to run from a cmd.exe shell to see if you get any output to the console.
5) When you say 'Python27.dll is the correct one' do you mean dependency walker is showing if finding the one in your installation directory?
6) Are you doing anything other than unzipping the downloaded file, and clicking on the Glade icon? I have not heard of this problem from other users, so it must be something peculiar to your setup.May 9, 2013 at 8:15 am #1365
1) No popup dialogs
2) When Glade starts, the first thing it does after setting up the logfile is to initialise Python using Py_Initialize. If Python fails to initialise, it will exit with no warning. Unable to understand this step.
3) I can't see the app at all.
4) Even from cmd.exe I can't see any log/output err
5) Yes, dependencywalker shows me that the python27.dll file is pointing to the one in the installation directory
6) I unzipped the package and double-clicked on glade. No results. At the second try, I installed the vcredist_x86.exe and double-clicked on glade. Non results again. At the third chance, I read the README file and setup the environment variables. No success again.
[/quote]May 9, 2013 at 8:45 am #1366
Hmm, can you start Windows Event Viewer and expand Windows Logs->Application? Then see if there are any events for Glade, if so click on them and they should show some details about the issue.
Also can you confirm you have no C:WindowsSystem32python27.dll or C:WindowssysWOW64python27.dll?May 10, 2013 at 6:33 am #1367
Ok! Glade starts! And it is very amazing…
The problem is that I was using the python27.dll provided with glade installation.
I just copied the file FROM C:WindowsSystem32python27.dll TO <pathToGlade>.
Glade starts! I will let you notice in case of issues.
P.S.: I have a 32bit Windows7May 10, 2013 at 8:08 am #1368
And what do you see in the logfile – something like:
# Python version 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] for win32
- You must be logged in to reply to this topic.