Since I build my own Qt across platforms (I'm the Qt build monkey for my project), I had the .pdbs already.  For me, it was just a matter of not second-guessingCreator.

On 7/17/2018 12:00 PM, Michael Jackson wrote:
We used to use the online installer when we were building up an SDK for our 
project but it just crashes most of the time on Windows so we switched to using 
the full download installer. We use CMake to drive the entire process including 
launching the Qt installer using a javascript file. (Better documentation for 
that would also be helpful). If you are curious as to our use case you can see 
it here:

http://www.github.com/bluequartzsoftware/DREAM3DSuperbuild

If I can go back to using the online installer (must work on Windows 10 
(pro)/8/7) which would install the PDB files that would be great. Can you 
package the PDB files using an installer like for Qt itself? At least that 
would make the installation go much quicker and easier.


--
Michael Jackson | Owner, President
       BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net <http://www.bluequartz.net>

On 7/17/18, 1:00 AM, "David Schulz" <david.sch...@qt.io> wrote:

     Hi,
I totally agree with you here, that was the reason for creating https://bugreports.qt.io/browse/QTBUG-67587. So if you both would leave a comment/vote on that report someone might look into this mess. > I don't think I remember ever having to do this with Visual Studio but I'll bite. The change that introduced this behavior is relative new and would also effect a setup with visual studio, because the symbol files are also missing there. "offline installer would be too big with PDB files & we just can't create it" was the statement. BTW: The online installer is not affected by this. Greetings David -----Original Message-----
     From: Qt-creator 
[mailto:qt-creator-bounces+david.schulz=qt...@qt-project.org] On Behalf Of 
Michael Jackson
     Sent: Monday, July 16, 2018 19:07
     To: Bob Hood <bho...@comcast.net>; qt-creator@qt-project.org
     Subject: Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?
I ended up getting them installed (clunky way to install them) and then created a rule set in CMake to copy them to my local binary directory of the app that I am compiling. Maybe instead of packaging them as a single archive of a single folder it would be better to create the proper sub-folders then create the archive. I had to individually select each .7z file for VS2017 and decompress them. Would be easier, I would think, to just be able to decompress the archive as it sites in Qt5.10.1/5.10.1 folder and everything gets put into the proper location.
     --
     Michael Jackson | Owner, President
           BlueQuartz Software
     [e] mike.jack...@bluequartz.net
     [w] www.bluequartz.net <http://www.bluequartz.net>
On 7/14/18, 6:02 PM, "Bob Hood" <bho...@comcast.net> wrote: Mine are in the Qt installation (the one that my Creator kit points to), in
         the bin\ folder, right along side the Qt5 .dll files.
On 7/13/2018 12:22 PM, Michael Jackson wrote:
         > I don't think I remember ever having to do this with Visual Studio 
but I'll bite. So I downloaded the pdb zip file? I have Qt 5.10.1 with VS2017 x64. 
Where do I install the pdb files? My build dir? Or somewhere in the Qt5 
installation?
         >
         > Thanks
         >
         > --
         > Michael Jackson | Owner, President
         >        BlueQuartz Software
         > [e] mike.jack...@bluequartz.net
         > [w] www.bluequartz.net <http://www.bluequartz.net>
         >
         > On 7/13/18, 12:38 PM, "Qt-creator on behalf of Bob Hood" 
<qt-creator-bounces+mike.jackson=bluequartz....@qt-project.org on behalf of 
bho...@comcast.net> wrote:
         >
         >      Ah!  That was indeed the problem (and hopefully Micheal's as 
well).  My debug\
         >      folder had Qt5 DLLs sitting in it, because I mistakenly assumed 
they had to be
         >      there in order for debugging to work.  When I deleted them, 
Creator used the
         >      kit path, and found the *.pdb file it needed.  I can now see 
QStrings.
         >
         >      This was pilot error.  Creator was not at fault.  Sorry for the 
noise.
         >
         >
         >      On 7/12/2018 11:12 PM, David Schulz wrote:
         >      > Hi,
         >      >
         >      > cdb can't find the pdb file for 
W:\Dev\Personal\Projects\Qt\Skoop\client\debug\Qt5Cored.dll. Do you know where that 
file is on your hard disk?
         >      >
         >      > And please create a  bug report for this issue, so we can 
move the discussion to jira.
         >      >
         >      > Greetings
         >      > David
         >      >
         >      > -----Original Message-----
         >      > From: Qt-creator 
[mailto:qt-creator-bounces+david.schulz=qt...@qt-project.org] On Behalf Of Bob Hood
         >      > Sent: Friday, July 13, 2018 04:30
         >      > To: qt-creator@qt-project.org
         >      > Subject: Re: [Qt-creator] QString "not accessible" in Creator 
4.6.2?
         >      >
         >      > https://pastebin.com/z2eZxVuu
         >      >
         >      >
         >      > On 7/9/2018 5:10 AM, David Schulz wrote:
         >      >> Hi,
         >      >>
         >      >> I've checked 4.6.2 and 4.7 with a Qt based on msvc 2017 
WindowsSDKVersion 10.0.17134.0 and I get sensible dumper values in the locals and 
expression view.
         >      >> Can you share the content of the debugger log (Window > Views 
> Debugger Log) on your codepaster of choice?
         >      >>
         >      >> Greetings
         >      >> David
         >      >>
         >      >> -----Original Message-----
         >      >> From: Qt-creator 
[mailto:qt-creator-bounces+david.schulz=qt...@qt-project.org] On Behalf Of Bob Hood
         >      >> Sent: Saturday, July 7, 2018 15:36
         >      >> To: qt-creator@qt-project.org
         >      >> Subject: Re: [Qt-creator] QString "not accessible" in 
Creator 4.6.2?
         >      >>
         >      >> So only Michael and I are experiencing this?  Or is that 
only Michael and I are using 4.6.2 on Windows?
         >      >>
         >      >>
         >      >> On 7/6/2018 6:08 AM, Michael Jackson wrote:
         >      >>> I also just happened to setup QtCreator 4.6.2 and I had the 
same issue. Latest VS2017 release running on Windows 10 x64.
         >      >>> --
         >      >>> Michael Jackson | Owner, President
         >      >>>          BlueQuartz Software
         >      >>> [e] mike.jack...@bluequartz.net
         >      >>> [w] www.bluequartz.net
         >      >>>
         >      >>> On 7/5/18, 6:49 PM, "Qt-creator on behalf of Bob Hood" 
<qt-creator-bounces+mike.jackson=bluequartz....@qt-project.org on behalf of bho...@comcast.net> wrote:
         >      >>>
         >      >>>        I have installed Creator 4.6.2 (normally, I use 
4.0.3) and have started a new
         >      >>>        project with it.  Prior to installing it, I already 
had Visual Studio 2017
         >      >>>        15.4.7 installed, along with Windows SDK v10.1.17134.12 
with "Debugging Tools
         >      >>>        for Windows".  Creator 4.6.2 automatically found the 
debugging tools, and I
         >      >>>        reconfigured my Kits accordingly for use with Qt 
5.9.4 Desktop (which I built
         >      >>>        myself using Visual Studio 2017, so they are ABI 
compatible).
         >      >>>
         >      >>>        I'm debugging into my Qt application, and I'm getting 
"not accessible" the
         >      >>>        Locals pane for QString and QStringList.  Was there 
some further set-up I
         >      >>>        needed to perform?  I don't recall having this issue 
with 4.0.3.
         >      >>>        _______________________________________________
         >      >>>        Qt-creator mailing list
         >      >>>        Qt-creator@qt-project.org
         >      >>>        
http://lists.qt-project.org/mailman/listinfo/qt-creator
         >      >>>
         >      >>>
         >      >>>
         >      >>> _______________________________________________
         >      >>> Qt-creator mailing list
         >      >>> Qt-creator@qt-project.org
         >      >>> http://lists.qt-project.org/mailman/listinfo/qt-creator
         >      >> _______________________________________________
         >      >> Qt-creator mailing list
         >      >> Qt-creator@qt-project.org
         >      >> http://lists.qt-project.org/mailman/listinfo/qt-creator
         >      >> _______________________________________________
         >      >> Qt-creator mailing list
         >      >> Qt-creator@qt-project.org
         >      >> http://lists.qt-project.org/mailman/listinfo/qt-creator
         >      > _______________________________________________
         >      > Qt-creator mailing list
         >      > Qt-creator@qt-project.org
         >      > http://lists.qt-project.org/mailman/listinfo/qt-creator
         >
         >      _______________________________________________
         >      Qt-creator mailing list
         >      Qt-creator@qt-project.org
         >      http://lists.qt-project.org/mailman/listinfo/qt-creator
         >
         >
         >
         >
_______________________________________________
     Qt-creator mailing list
     Qt-creator@qt-project.org
     http://lists.qt-project.org/mailman/listinfo/qt-creator

_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to