Re: [Qt-creator] QString "not accessible" in Creator 4.6.2?

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"

Re: [Qt-creator] How to put custom build steps into Git?

> Can you make use of the .pro.shared file for that? > http://doc.qt.io/qtcreator/creator-sharing-project-settings.html I just stumbled across that option yesterday, and I'm trying to work through it to see if it works. Based on where those values are placed in the .pro.user file, I'm not sure

Re: [Qt-creator] How to put custom build steps into Git?

Yeah, that’s what my current .exe does, it grabs the information from Git and parses the previously existing version.h (if one exists), only over-writing that header file if the Git information has changed from what’s in the file. Thus preventing a recompile of the much larger .cpp file that

Re: [Qt-creator] How to put custom build steps into Git?

> That is something that should be done by the build system IMHO Can you expand on this part? By build system, I assume you mean qmake? If that's what you meant, I'm all for doing it that way as well, how would I go about adding what I'm looking for into the .pro file? Basically, in our

Re: [Qt-creator] How to put custom build steps into Git?

On Fri, Jul 6, 2018 at 5:12 PM Murphy, Sean wrote: > > Can you make use of the .pro.shared file for that? > > http://doc.qt.io/qtcreator/creator-sharing-project-settings.html > > I just stumbled across that option yesterday, and I'm trying to work > through it > to see if it works. Based on

Re: [Qt-creator] How to put custom build steps into Git?

Another thing I didn't mention is that if you want to avoid rebuilding files, the script can be smarter. Generate to a temporary file and only copy it over the existing one if it is different. I didn't bother for my setup because the header is only included in one place and only rebuilds a small

Re: [Qt-creator] How to put custom build steps into Git?

On Fri, Jul 6, 2018 at 5:48 PM Murphy, Sean wrote: > > That is something that should be done by the build system IMHO > > Can you expand on this part? By build system, I assume you mean qmake? > If that's what you meant, I'm all for doing it that way as well, how would > I > go about adding what

Re: [Qt-creator] How to put custom build steps into Git?

This looks really promising, I’ll play around with this and see where I get. Sean Murphy Sr. Project Engineer Walbro LLC 4144 Doerr Rd Cass City, MI 48726 ph. 989 872 7274 cell 734 223 8975 fax. 989 872 3782 smur...@walbro.com Confidentiality Notice: The materials

Re: [Qt-creator] How to put custom build steps into Git?

For my git info, I am using what feels like a hacky way to avoid having to add pre-build steps on every single project configuration. Might help? In my .pro: # Get our build info from git OTHER_FILES += "$$PWD/gen_header.sh" !build_pass { UNUSED_RESULT = $$system(bash

Re: [Qt-creator] How to put custom build steps into Git?

On Fri, Jul 6, 2018 at 6:47 PM Murphy, Sean wrote: > Thanks guys! Actually I think a combination of both your suggestions might > work better than what I have currently. What I don’t like about my current > setup is that the thing that generates the .h file is an executable – it > has to be

Re: [Qt-creator] How to put custom build steps into Git?

Thanks guys! Actually I think a combination of both your suggestions might work better than what I have currently. What I don’t like about my current setup is that the thing that generates the .h file is an executable – it has to be compiled to work. The only real advantage of that is that it

Re: [Qt-creator] How to put custom build steps into Git?

On Donnerstag, 5. Juli 2018 20:46:51 CEST Murphy, Sean wrote: > For our project, we've got two build customizations that we do, that we'd > like to be able to put into source control, so that all developers > automatically get them. But it appears that adding those steps via Qt > Creator causes