Ok, I have that rule too, but does it re-invoke make after updating? It seems
to continue to process the old, out of date Makefile?
After
$(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
It either needs to say something like:
Makefile updated; run make again
or:
make
So:
$(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
make
True there is some risk of an infinite loop if the make `touch`es the Makefile,
to maybe there is a way to compare hashes?
> Sent: Wednesday, May 19, 2021 at 3:34 AM
> From: "Eike Ziller" <eike.zil...@qt.io>
> To: "Jason H" <jh...@gmx.com>
> Cc: "qt-creator" <qt-creator@qt-project.org>
> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
>
>
>
> > On May 18, 2021, at 18:58, Jason H <jh...@gmx.com> wrote:
> >
> >
> > So I am dumb. I forgot that among all those popups QtCreator gives you when
> > you save the .pro, running qmake is not one of them
> > I *thought* running qmake would have been automatic when the .pro changes.
> > (Or that the Makefile would pick up the .pro was modified and run qmake
> > automatically) but that doesn't seem to be the case?
> >
>
> The Makefile _should_ have a rule for re-running qmake when the .pro file is
> changed. My dummy project has
>
> Makefile: ../qmake_widgets/qmake_widgets.pro ……
> ...
> $(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
>
> Which is tricky because while running “make”, the Makefile is changed…. but
> it is supposed to work.
>
> Br, Eike
>
> >
> > Sent: Tuesday, May 18, 2021 at 11:53 AM
> > From: "Jason H" <jh...@gmx.com>
> > To: "Jason H" <jh...@gmx.com>
> > Cc: "qt-creator" <qt-creator@qt-project.org>
> > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > Accidentally only replied to Lars before, but for the list, for throughness:
> > Thanks Lars.
> >
> > I have added in the .pro
> > mac {
> > QMAKE_INFO_PLIST = macos/Info.plist
> > }
> >
> >
> > And the plist was copied from the build directory, added the key/string
> > pair:
> > <key>NSCameraUsageDescription</key>
> > <string>Reads Barcodes</string>
> >
> > And still no joy. The Info.plist in the package contents is not the one
> > with the added key.
> > I tried mac, macx, and macos for the platform in .pro. QtCreator shows int
> > he Project pane:
> > Other Files /
> > .. v macos
> > .... Info.plist
> >
> > So the file is there. It's just not being used. I have NOT set CONFIG -=
> > app_bundle. Looking at the compile output, Info.plist does not appear in
> > the compile output pane.
> >
> > It seems that something else is needed than QMAKE_INFO_PLIST?
> >
> > ...
> > ANSWER: Yes it needs a manual copy (currently). Then I filed
> > https://bugreports.qt.io/browse/QTBUG-93832
> >
> >
> > Sent: Tuesday, May 18, 2021 at 11:25 AM
> > From: "Jason H" <jh...@gmx.com>
> > To: "Lars Knoll" <lars.kn...@qt.io>
> > Cc: "qt-creator" <qt-creator@qt-project.org>
> > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > I got it working with a manual copy, but also filed:
> > https://bugreports.qt.io/browse/QTBUG-93832
> >
> >
> >
> > Sent: Tuesday, May 18, 2021 at 4:40 AM
> > From: "Lars Knoll" <lars.kn...@qt.io>
> > To: "Eike Ziller" <eike.zil...@qt.io>
> > Cc: "Jason H" <jh...@gmx.com>, "qt-creator" <qt-creator@qt-project.org>
> > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > On 17 May 2021, at 18:50, Eike Ziller <eike.zil...@qt.io> wrote:
> > On May 17, 2021, at 16:27, Jason H <jh...@gmx.com> wrote:
> >
> > Here is the question (asked by someone else) (Note this is specific to
> > *debugging* the app.)
> > https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
> > with no good resolution.
> >
> > It seems the way QtC is launching the debugger is running afoul of the
> > NSCameraUsageDescription. Has anyone else figured out a way around this?
> > I'm wondering if the Info.plist needs to be applied to LLDB somehow?
> >
> > I don’t quite understand if this is a Qt Creator specific issue or not.
> >
> > If the issue is that Qt Creator starts lldb, and lldb starts the app, maybe
> > running the app without debugging and then Debug > Start debugging > Attach
> > to running application helps.
> >
> > I’ve been doing some debugging of the camera on macOS lately. You do need
> > to add the Info.plist with
> > NSCameraUsageDescription/NSMicrophoneUsageDescription to your app to allow
> > camera/microphone access.
> >
> > After that, you might get a confirmation dialog to allow access on first
> > launch. Once that’s confirmed, you should be able to debug the app just
> > fine. At least it does work for me using Qt Creator.
> >
> > Cheers,
> > Lars
> >
> > _______________________________________________ Qt-creator mailing list
> > Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
> > _______________________________________________
> > Qt-creator mailing list
> > Qt-creator@qt-project.org
> > https://lists.qt-project.org/listinfo/qt-creator
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Erich-Thilo-Straße 10
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Jouni Lintunen
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg,
> HRB 144331 B
>
>
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
