On 31/03/2014 03:05, Edson W. R. Pereira wrote: Hi Edson,
Ok, that works but the dummy file in a subdirectory is looking more attractive by the minute.|win32 { system(...) }macx { system(...) } unix { system(...) }|
I think I will do that and add an INCLUDEPATH to it. That way it will help to deter anyone checking in a version in the top level source directory which would break the CMake build in a silent way.
Thanks for your input. 73 Bill G4WJS.
On Sun, Mar 30, 2014 at 11:01 PM, Bill Somerville <[email protected] <mailto:[email protected]>> wrote:On 31/03/2014 02:56, Edson W. R. Pereira wrote:Bill,Hi Edson,Have you tried qmake system() funcion?Not sure that directly helps me as I still have to find a command that will create a file in all platforms and environments.73, -- Edson73 Bill G4WJS.On Sun, Mar 30, 2014 at 10:49 PM, Bill Somerville <[email protected] <mailto:[email protected]>> wrote: Hi All, I have been struggling to find a way to get the CMake build and the qmake build to coexist without success so far. The problem is a file that the CMAke build generates in the build tree. It is called 'svnversion.h' and is included by C or C++ files that need to know the current svn revision. But in a qmake build no such file gets generated. I tried checking in a file called svnversion.h making sure that the CMake builds don't pick it up but that, I've just discovered, breaks the CMake build dependencies. So if anyone knows how to get qmake to generate a header file I would be most appreciative. The file doesn't have to contain anything, it just needs to exist somewhere sources compiled by qmake makefiles will include it. I suppose I could check one in in a subdirectory and change the qmake include paths to see it, does anyone have a better idea? 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/wsjt-devel------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
