Build: ok, run: not ok

[Pierre-Nicolas Rigal]

Found it.

In our .pro, we've the following

# Target configuration
!debug_and_release|build_pass {
  CONFIG(debug, debug|release): {
    unix:TARGET = $$member(TARGET, 0)_debug
    else:TARGET = $$member(TARGET, 0)d
  }
}

I think we copied this from some examples in the early Qt4 versions.

We use
DESTDIR = ./bin

and then we have both debug and release executable in the same directory.

With WinCE, this leads to the following situation:
QtDLLs are copied to <program files>/gdc directory
gdcd.exe is copied to <program files>/gdcd directory

therefore it doesn't work.

I commented the .pro part and now it works better (at least I can debug it).
Thanks Espen for the hint.

Now I get an ASSERT, but at least I can debug the tool.
I'll go further and come back.

Thanks again and sorry for the stupid issue.

Pn

-----Original Message-----
From: Espen Riskedal [mailto:espenr at trolltech.com] 
Sent: lundi 22 octobre 2007 11:04
To: Marius Storm-Olsen
Cc: Pierre-Nicolas Rigal; qtce-preview-feedback at trolltech.com
Subject: Re: Build: ok, run: not ok

Marius Storm-Olsen wrote:
> Pierre-Nicolas Rigal said the following on 22.10.2007 10:14:
>> Unfortunately, on my side this is not the case for me. I'm using a
>> Qt application (dynamically linked), and the DLLs are automatically
>> deployed.
>>
>> I compared lineedits demo and my app with depends: they look very
>> similar (I use more Qt DLLs than the lineedits demo), but mine is 
>> still not working.
>>
>> If I run it in Debug mode, I get the error message described
>> previously ; if I run it in Release mode, I get a crash, but the
>> stack trace is, of course, unreadable.
>>
>> I'll start commenting code to see what's going wrong, but I fear
>> this will be a huge task :(.
>>
>> BTW: I moved to 4.3CE-tp1 version, but without change.
> 
> Maybe your device is missing the MSVC runtimes to run the application, 
> and it's DLLs?
> 
> Have you run any Qt application on your device, so you know that the 
> runtimes are there? If not, you'd probably want to manually deploy the 
> runtimes on your device first. You'll find the runtimes in:
>     <VisualStudio>/vc/ce/dll/<arch>/*

Why don't you list us the dlls you have in your application directory on 
the device, and also the ones that are in the lineedit directory so we 
can see what is or isn't there.

espen

To unsubscribe - send "unsubscribe" in the subject to qtce-preview-feedback-request at trolltech.com