Build: ok, run: not ok

[George Staikos]

On 26-Oct-07, at 2:50 AM, Maurice Kalinowski wrote:

> George Staikos wrote:
>>
>> On 23-Oct-07, at 8:20 AM, Maurice Kalinowski wrote:
>>
>>> Hi,
>>>>
>>>>   We're getting close but still not there.  It doesn't seem  
>>>> possible to specify paths to DEPLOYMENT?  At least that's my  
>>>> guess.  If I edit the .vcproj and edit the additional  
>>>> deployments manually then Visual Studio works.  However qmake  
>>>> never seems to add those deployments to my vcproj.  It will  
>>>> however complain if I leave out the .path value.  Maybe I have  
>>>> to specify something to tell it where to get the files, and then  
>>>> specify a relative path?
>>>>
>>> it should be possible to do that. The .path part of setting this  
>>> variable can be used in two different ways.
>>> 1.) specify a path which is absolute on the device, like \Windows  
>>> for Qt libraries
>>> 2.) specify a path relative to the application destination. That  
>>> is the same like Visual Studio uses and is called \% 
>>> CSIDL_PROGRAMFILES%\<target>, where the first example usually  
>>> gets expanded to "\Program Files" and the second is the TARGET  
>>> you specify in your .pro file.
>>>
>>> To identify, where the file is on your development system, you  
>>> use the .sources argument and specify them relative to your  
>>> working directory or absolute.
>>>
>>> So, to summarize, .sources describes the location on your local  
>>> hard disk, where .path means the location on your Windows CE  
>>> device. It is true, that the output of qmake is not very verbose,  
>>> I might need to add some additional lines there.
>>
>>   This is what I'm trying but it doesn't help.  If I manually edit  
>> the vcproj I can add in the additional files but QMake never picks  
>> them up on its own.  It's not the .path that's the issue, it's  
>> the .sources.  It doesn't seem to see them.
> Let me ask you some things about the structure of your project. I  
> assume you have multiple project, which are combined by a toplevel  
> pro-file. Where do you add the deployment rules? How deep is it  
> within the structure of your build system. The usual way people  
> tend to things is:
>
> top.pro
>   -> src.pro (in directory src)
>   -> somestuff.pro ( appropriate directory)
>   -> plugins.pro
>        -> plugin1.pro
>        -> plugin2.pro
>
>
> I am just curious to be able to reproduce your issues here.

    I have one project that builds my libraries which link to Qt.   
Then I have another separate project that builds the app and includes  
the library that is already built.  There is no single top-level .pro.

--
George Staikos
Staikos Computing Services Inc.      http://www.staikos.net/