www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - Problems building Qtd on Windows

reply simendsjo <simendsjo gmail.com> writes:
I'm trying to compile Qtd trunk on QT 4.7 using dmd 2.054, but I'm 
getting a strange error:

-- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe -- broken

   The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to 
compile a
   simple test program.

But I'm able to compile a small program, t.c:
int main() { return 0; }
g++ t.c
a.exe // works

Here's the full output:

c:\d\ext\qtd\dmd-2.054>cmake -G"MinGW Makefiles" ../ 
-DCMAKE_CXX_FLAGS="-m32"

-- The CXX compiler identification is GNU
-- The C compiler identification is GNU
-- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe
-- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe -- broken
CMake Error at C:/Program Files (x86)/CMake 
2.8/share/cmake-2.8/Modules/CMakeTes
tCXXCompiler.cmake:45 (MESSAGE):
   The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to 
compile a
   simple test program.

   It fails with the following output:

    Change Dir: C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp



   Run Build Command:c:/Qt/2010.05/mingw/bin/mingw32-make.exe
   "cmTryCompileExec/fast"

   c:/Qt/2010.05/mingw/bin/mingw32-make.exe -f
   CMakeFiles\cmTryCompileExec.dir\build.make
   CMakeFiles/cmTryCompileExec.dir/build

   mingw32-make.exe[1]: Entering directory
   `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

   "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_progress_report
   C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\CMakeFiles 1

   Building CXX object
   CMakeFiles/cmTryCompileExec.dir/testCXXCompiler.cxx.obj

   c:\Qt\2010.05\mingw\bin\g++.exe -m32 -o
   CMakeFiles\cmTryCompileExec.dir\testCXXCompiler.cxx.obj -c
   C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\testCXXCompiler.cxx

   Linking CXX executable cmTryCompileExec.exe

   "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
   CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

   Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

   mingw32-make.exe[1]: *** [cmTryCompileExec.exe] Error 1

   mingw32-make.exe[1]: Leaving directory
   `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

   mingw32-make.exe: *** [cmTryCompileExec/fast] Error 2





   CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
   CMakeLists.txt:2 (PROJECT)


-- Configuring incomplete, errors occurred!
Jul 19 2011
parent reply simendsjo <simendsjo gmail.com> writes:
On 19.07.2011 10:23, simendsjo wrote:
 I'm trying to compile Qtd trunk on QT 4.7 using dmd 2.054, but I'm
 getting a strange error:

 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken

 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to compile a
 simple test program.

 But I'm able to compile a small program, t.c:
 int main() { return 0; }
 g++ t.c
 a.exe // works

 Here's the full output:

 c:\d\ext\qtd\dmd-2.054>cmake -G"MinGW Makefiles" ../
 -DCMAKE_CXX_FLAGS="-m32"

 -- The CXX compiler identification is GNU
 -- The C compiler identification is GNU
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken
 CMake Error at C:/Program Files (x86)/CMake
 2.8/share/cmake-2.8/Modules/CMakeTes
 tCXXCompiler.cmake:45 (MESSAGE):
 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to compile a
 simple test program.

 It fails with the following output:

 Change Dir: C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp



 Run Build Command:c:/Qt/2010.05/mingw/bin/mingw32-make.exe
 "cmTryCompileExec/fast"

 c:/Qt/2010.05/mingw/bin/mingw32-make.exe -f
 CMakeFiles\cmTryCompileExec.dir\build.make
 CMakeFiles/cmTryCompileExec.dir/build

 mingw32-make.exe[1]: Entering directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_progress_report
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\CMakeFiles 1

 Building CXX object
 CMakeFiles/cmTryCompileExec.dir/testCXXCompiler.cxx.obj

 c:\Qt\2010.05\mingw\bin\g++.exe -m32 -o
 CMakeFiles\cmTryCompileExec.dir\testCXXCompiler.cxx.obj -c
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\testCXXCompiler.cxx

 Linking CXX executable cmTryCompileExec.exe

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
 CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

 Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

 mingw32-make.exe[1]: *** [cmTryCompileExec.exe] Error 1

 mingw32-make.exe[1]: Leaving directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 mingw32-make.exe: *** [cmTryCompileExec/fast] Error 2





 CMake will not be able to correctly generate this project.
 Call Stack (most recent call first):
 CMakeLists.txt:2 (PROJECT)


 -- Configuring incomplete, errors occurred!

The steps works while running manually:
 mingw32-make.exe[1]: Entering directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
 CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

 Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

But if I do this manually: cd CMakeFiles\CMakeTmp cmake -E cmake_link_script CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1 It works and I get a cmTryCompileExec.exe. Does it have some problems with the relative path? Any workaround for this? This is using cmake 2.8.5
Jul 19 2011
next sibling parent reply simendsjo <simendsjo gmail.com> writes:
On 19.07.2011 11:20, simendsjo wrote:
 On 19.07.2011 10:23, simendsjo wrote:
 I'm trying to compile Qtd trunk on QT 4.7 using dmd 2.054, but I'm
 getting a strange error:

 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken

 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to
 compile a
 simple test program.

 But I'm able to compile a small program, t.c:
 int main() { return 0; }
 g++ t.c
 a.exe // works

 Here's the full output:

 c:\d\ext\qtd\dmd-2.054>cmake -G"MinGW Makefiles" ../
 -DCMAKE_CXX_FLAGS="-m32"

 -- The CXX compiler identification is GNU
 -- The C compiler identification is GNU
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken
 CMake Error at C:/Program Files (x86)/CMake
 2.8/share/cmake-2.8/Modules/CMakeTes
 tCXXCompiler.cmake:45 (MESSAGE):
 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to
 compile a
 simple test program.

 It fails with the following output:

 Change Dir: C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp



 Run Build Command:c:/Qt/2010.05/mingw/bin/mingw32-make.exe
 "cmTryCompileExec/fast"

 c:/Qt/2010.05/mingw/bin/mingw32-make.exe -f
 CMakeFiles\cmTryCompileExec.dir\build.make
 CMakeFiles/cmTryCompileExec.dir/build

 mingw32-make.exe[1]: Entering directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_progress_report
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\CMakeFiles 1

 Building CXX object
 CMakeFiles/cmTryCompileExec.dir/testCXXCompiler.cxx.obj

 c:\Qt\2010.05\mingw\bin\g++.exe -m32 -o
 CMakeFiles\cmTryCompileExec.dir\testCXXCompiler.cxx.obj -c
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\testCXXCompiler.cxx

 Linking CXX executable cmTryCompileExec.exe

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
 CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

 Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

 mingw32-make.exe[1]: *** [cmTryCompileExec.exe] Error 1

 mingw32-make.exe[1]: Leaving directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 mingw32-make.exe: *** [cmTryCompileExec/fast] Error 2





 CMake will not be able to correctly generate this project.
 Call Stack (most recent call first):
 CMakeLists.txt:2 (PROJECT)


 -- Configuring incomplete, errors occurred!

The steps works while running manually: > mingw32-make.exe[1]: Entering directory > `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp' (...) > "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script > CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1 > > Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt" But if I do this manually: cd CMakeFiles\CMakeTmp cmake -E cmake_link_script CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1 It works and I get a cmTryCompileExec.exe. Does it have some problems with the relative path? Any workaround for this? This is using cmake 2.8.5

I've also tried cmake 2.6 without any luck. I forced the "try compile" stuff to report as succeeded by modifying CMakeTestCXXCompiler.cmake and CMakeTestCCompiler.cmake. This allowed me to begin compilation, but the underlying problem is not gone, and linking fails during compilation: Linking CXX shared library lib\libcpp_core.dll Error opening link script "CMakeFiles\cpp_core.dir\link.txt" mingw32-make[5]: *** [lib/libcpp_core.dll] Error 1 mingw32-make[4]: *** [CMakeFiles/cpp_core.dir/all] Error 2 mingw32-make[3]: *** [all] Error 2 mingw32-make[2]: *** [main] Error 2 mingw32-make[1]: *** [CMakeFiles/main.dir/all] Error 2 mingw32-make: *** [all] Error 2
Jul 19 2011
parent reply simendsjo <simendsjo gmail.com> writes:
On 19.07.2011 11:56, simendsjo wrote:
 On 19.07.2011 11:20, simendsjo wrote:
 On 19.07.2011 10:23, simendsjo wrote:
 I'm trying to compile Qtd trunk on QT 4.7 using dmd 2.054, but I'm
 getting a strange error:

 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken

 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to
 compile a
 simple test program.

 But I'm able to compile a small program, t.c:
 int main() { return 0; }
 g++ t.c
 a.exe // works

 Here's the full output:

 c:\d\ext\qtd\dmd-2.054>cmake -G"MinGW Makefiles" ../
 -DCMAKE_CXX_FLAGS="-m32"

 -- The CXX compiler identification is GNU
 -- The C compiler identification is GNU
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken
 CMake Error at C:/Program Files (x86)/CMake
 2.8/share/cmake-2.8/Modules/CMakeTes
 tCXXCompiler.cmake:45 (MESSAGE):
 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to
 compile a
 simple test program.

 It fails with the following output:

 Change Dir: C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp



 Run Build Command:c:/Qt/2010.05/mingw/bin/mingw32-make.exe
 "cmTryCompileExec/fast"

 c:/Qt/2010.05/mingw/bin/mingw32-make.exe -f
 CMakeFiles\cmTryCompileExec.dir\build.make
 CMakeFiles/cmTryCompileExec.dir/build

 mingw32-make.exe[1]: Entering directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E
 cmake_progress_report
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\CMakeFiles 1

 Building CXX object
 CMakeFiles/cmTryCompileExec.dir/testCXXCompiler.cxx.obj

 c:\Qt\2010.05\mingw\bin\g++.exe -m32 -o
 CMakeFiles\cmTryCompileExec.dir\testCXXCompiler.cxx.obj -c
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\testCXXCompiler.cxx

 Linking CXX executable cmTryCompileExec.exe

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
 CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

 Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

 mingw32-make.exe[1]: *** [cmTryCompileExec.exe] Error 1

 mingw32-make.exe[1]: Leaving directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 mingw32-make.exe: *** [cmTryCompileExec/fast] Error 2





 CMake will not be able to correctly generate this project.
 Call Stack (most recent call first):
 CMakeLists.txt:2 (PROJECT)


 -- Configuring incomplete, errors occurred!

The steps works while running manually:
 mingw32-make.exe[1]: Entering directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
 CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

 Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

But if I do this manually: cd CMakeFiles\CMakeTmp cmake -E cmake_link_script CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1 It works and I get a cmTryCompileExec.exe. Does it have some problems with the relative path? Any workaround for this? This is using cmake 2.8.5

I've also tried cmake 2.6 without any luck. I forced the "try compile" stuff to report as succeeded by modifying CMakeTestCXXCompiler.cmake and CMakeTestCCompiler.cmake. This allowed me to begin compilation, but the underlying problem is not gone, and linking fails during compilation: Linking CXX shared library lib\libcpp_core.dll Error opening link script "CMakeFiles\cpp_core.dir\link.txt" mingw32-make[5]: *** [lib/libcpp_core.dll] Error 1 mingw32-make[4]: *** [CMakeFiles/cpp_core.dir/all] Error 2 mingw32-make[3]: *** [all] Error 2 mingw32-make[2]: *** [main] Error 2 mingw32-make[1]: *** [CMakeFiles/main.dir/all] Error 2 mingw32-make: *** [all] Error 2

Trying SO: http://stackoverflow.com/questions/6745911/cmake-error-opening-link-script-cannot-change-directory
Jul 19 2011
parent reply simendsjo <simendsjo gmail.com> writes:
On 19.07.2011 12:45, simendsjo wrote:
 On 19.07.2011 11:56, simendsjo wrote:
 On 19.07.2011 11:20, simendsjo wrote:
 On 19.07.2011 10:23, simendsjo wrote:
 I'm trying to compile Qtd trunk on QT 4.7 using dmd 2.054, but I'm
 getting a strange error:

 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken

 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to
 compile a
 simple test program.

 But I'm able to compile a small program, t.c:
 int main() { return 0; }
 g++ t.c
 a.exe // works

 Here's the full output:

 c:\d\ext\qtd\dmd-2.054>cmake -G"MinGW Makefiles" ../
 -DCMAKE_CXX_FLAGS="-m32"

 -- The CXX compiler identification is GNU
 -- The C compiler identification is GNU
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe
 -- Check for working CXX compiler: c:/Qt/2010.05/mingw/bin/g++.exe --
 broken
 CMake Error at C:/Program Files (x86)/CMake
 2.8/share/cmake-2.8/Modules/CMakeTes
 tCXXCompiler.cmake:45 (MESSAGE):
 The C++ compiler "c:/Qt/2010.05/mingw/bin/g++.exe" is not able to
 compile a
 simple test program.

 It fails with the following output:

 Change Dir: C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp



 Run Build Command:c:/Qt/2010.05/mingw/bin/mingw32-make.exe
 "cmTryCompileExec/fast"

 c:/Qt/2010.05/mingw/bin/mingw32-make.exe -f
 CMakeFiles\cmTryCompileExec.dir\build.make
 CMakeFiles/cmTryCompileExec.dir/build

 mingw32-make.exe[1]: Entering directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E
 cmake_progress_report
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\CMakeFiles 1

 Building CXX object
 CMakeFiles/cmTryCompileExec.dir/testCXXCompiler.cxx.obj

 c:\Qt\2010.05\mingw\bin\g++.exe -m32 -o
 CMakeFiles\cmTryCompileExec.dir\testCXXCompiler.cxx.obj -c
 C:\d\ext\qtd\dmd-2.054\CMakeFiles\CMakeTmp\testCXXCompiler.cxx

 Linking CXX executable cmTryCompileExec.exe

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
 CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

 Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

 mingw32-make.exe[1]: *** [cmTryCompileExec.exe] Error 1

 mingw32-make.exe[1]: Leaving directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 mingw32-make.exe: *** [cmTryCompileExec/fast] Error 2





 CMake will not be able to correctly generate this project.
 Call Stack (most recent call first):
 CMakeLists.txt:2 (PROJECT)


 -- Configuring incomplete, errors occurred!

The steps works while running manually:
 mingw32-make.exe[1]: Entering directory
 `C:/d/ext/qtd/dmd-2.054/CMakeFiles/CMakeTmp'

 "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E cmake_link_script
 CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1

 Error opening link script "CMakeFiles\cmTryCompileExec.dir\link.txt"

But if I do this manually: cd CMakeFiles\CMakeTmp cmake -E cmake_link_script CMakeFiles\cmTryCompileExec.dir\link.txt --verbose=1 It works and I get a cmTryCompileExec.exe. Does it have some problems with the relative path? Any workaround for this? This is using cmake 2.8.5

I've also tried cmake 2.6 without any luck. I forced the "try compile" stuff to report as succeeded by modifying CMakeTestCXXCompiler.cmake and CMakeTestCCompiler.cmake. This allowed me to begin compilation, but the underlying problem is not gone, and linking fails during compilation: Linking CXX shared library lib\libcpp_core.dll Error opening link script "CMakeFiles\cpp_core.dir\link.txt" mingw32-make[5]: *** [lib/libcpp_core.dll] Error 1 mingw32-make[4]: *** [CMakeFiles/cpp_core.dir/all] Error 2 mingw32-make[3]: *** [all] Error 2 mingw32-make[2]: *** [main] Error 2 mingw32-make[1]: *** [CMakeFiles/main.dir/all] Error 2 mingw32-make: *** [all] Error 2

Trying SO: http://stackoverflow.com/questions/6745911/cmake-error-opening-link-script-cannot-change-directory

Giving up... Tried 3 versions of qt + 2 of cmake + 2 of qtd. Is windows not supported anymore?
Jul 19 2011
parent reply simendsjo <simendsjo gmail.com> writes:
On 19.07.2011 14:46, Trass3r wrote:
 Giving up... Tried 3 versions of qt + 2 of cmake + 2 of qtd.
 Is windows not supported anymore?

Was it ever? I always hit that: http://dsource.org/projects/qtd/ticket/54

I made it "work" (read: compile and crash on application start) on Win7x86 a while ago. My problem was some programs build on Qt on the path before the SDK, so the wrong DLL was picked up.
Jul 19 2011
parent reply David Nadlinger <see klickverbot.at> writes:
On 7/20/11 12:37 AM, Andrej Mitrovic wrote:
 I had a bunch of runtime crashes when I last used QtD, and I've
 reported this. But QtD seems to be staling again, there's hardly
 anyone working on it. And how can anyone work on it when the porting
 process is not documented..

Which kind of documentation for the »porting process« would you like to see? As with a lot of other promising D projects (e.g. LDC), the main problem of QtD is manpower (or rather, the lack thereof), so it would be great if you could help making QtD development more accessible. The code generator part of the bindings started out as a fork of Qt Jambi (Qt Java bindings, http://qt-jambi.org/), so you might find some information there. Unfortunately, I didn't find time for extensive work on QtD for quite some while now (it just works for my applications), but I'd be happy to answer any questions (just drop by in #qtd, I am there quite frequently). David
Jul 20 2011
parent David Nadlinger <see klickverbot.at> writes:
On 7/21/11 2:14 AM, Andrej Mitrovic wrote:
 Ok, but the other CTFE issues are still there:

 D:\dev\projects\qtd\examples\desktop\systray>dmd -unittest
 -version=QtdUnittest -I..\..\..\build_dir\build -I..\..\..\d2
 ..\..\..\build_dir\build\lib\qtdcore.lib
 ..\..\..\build_dir\build\lib\qtdgui.lib qrc_systray.d window.d main.d
 -ofsystray
 ..\..\..\d2\qtd\MOC.d(271): Error: gen.output ~= format_ctfe("\x0a //
 content:\x0a") cannot be evaluated
 at compile time
 ..\..\..\d2\qtd\MOC.d(272): Error: cannot evaluate format_ctfe("
 ${},       // revision\x0a",2) at compile time
 ..\..\..\d2\qtd\MOC.d(484): Error: cannot evaluate generateCode(gen)
 at compile time
 ..\..\..\d2\qtd\MOC.d(513): Error: cannot evaluate generateMetaInfo()
 at compile time
 ..\..\..\d2\qtd\MOC.d(513): Error: argument to mixin must be a string,
 not (generateMetaInfo())

Well, seems like I never built one of my applications since the CTFE overhaul was merged into master… ;) It would be great if you could have a short look at what actually got broken. qtd.MOC is hand-written, so tracking that CTFE regression [1] down without going insane should be possible. By the way, pretty much all of my QtD code is D2. If you don't have time for it, I will definitely have a look at it at some point in the future, but after my Thrift project, updating LDC 2 is currently on top of my todo list. Thanks, David [1] From a DMD development perspective, it might be that this isn't a regressions because the feature might not have worked correctly before, but it certainly did the job. If I were to make a wild guess, I'd try manually setting gen.output to [] if it should be null at that point, because I had a similar problem after the overhaul with strings, but as this is supposed to be fixed, it's probably something else.
Jul 20 2011
prev sibling next sibling parent Trass3r <un known.com> writes:
 Giving up... Tried 3 versions of qt + 2 of cmake + 2 of qtd.
 Is windows not supported anymore?

Was it ever? I always hit that: http://dsource.org/projects/qtd/ticket/54
Jul 19 2011
prev sibling next sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
I had a bunch of runtime crashes when I last used QtD, and I've
reported this. But QtD seems to be staling again, there's hardly
anyone working on it. And how can anyone work on it when the porting
process is not documented..
Jul 19 2011
prev sibling next sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
On 7/20/11, David Nadlinger <see klickverbot.at> wrote:
 The code generator part of the bindings started out as a fork of Qt
 Jambi (Qt Java bindings, http://qt-jambi.org/), so you might find some
 information there.

Hmm ok, I'll read about it.
 Unfortunately, I didn't find time for extensive work on QtD for quite
 some while now (it just works for my applications), but I'd be happy to
 answer any questions (just drop by in #qtd, I am there quite frequently).

 David

Yeah I know you're busy with that GSOC project, which is a pretty cool project. Whatever happened to the rest of the QtD team though? They said they've frozen QtD, then unfrozen again, but now it seems kind of idle with nobody around. Btw, it could be that the bugs were related to DMD and not Qt itself. The last DMD I've tried was 2.052. I'll give a shot with a newer DMD and figure out what's causing the bugs if they're still there.
Jul 20 2011
prev sibling next sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
Well now I can't even compile the example which used to crash at runtime:
http://codepad.org/Dh9fjQKG

This is while trying to compile the project in the attachment in this ticket:
http://www.dsource.org/projects/qtd/ticket/85
Jul 20 2011
prev sibling next sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
Btw that's using 2.054 on XP32.
Jul 20 2011
prev sibling next sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
Also I don't understand this, see changeset 411:

 hg log -r :

changeset: 411:6fe37cbd9510 user: David Nadlinger <code klickverbot.at> date: Mon Apr 18 00:16:33 2011 +0200 summary: Octal literals have been deprecated, fix build. changeset: 412:4189f1d51a7d user: Max Samukha <maxsamukha gmail.com> date: Thu May 05 20:11:26 2011 +0300 summary: support for new dmd naming changeset: 413:bdc08c8391ad user: Max Samukha <maxsamukha gmail.com> date: Thu May 05 22:32:50 2011 +0300 summary: removed unnecessary regex grouping changeset: 414:b2a803c73b89 tag: tip user: David Nadlinger <code klickverbot.at> date: Fri May 06 13:39:49 2011 +0200 summary: Declare tabArray const. So now I'm at 414, and when I try to build: D:\dev\projects\qtd\examples\desktop\systray>build D:\dev\projects\qtd\examples\desktop\systray>..\..\..\tools\drcc\drcc systray.qrc 1>qrc_systray.d D:\dev\projects\qtd\examples\desktop\systray>dmd -unittest -version=QtdUnittest -ID:\dev\lib\D\qtd\build_dir\build -ID:\dev\lib\D\qtd\d2 ..\..\..\build_dir\build\lib\qtdcore.lib ..\..\..\build_dir\build\lib\qtdgui.lib qrc_systray.d window.d main.d -ofsystray D:\dev\lib\D\qtd\d2\qtd\ctfe\Integer.d(157): octal literals 0123 are deprecated, use std.conv.octal!123 instead D:\dev\lib\D\qtd\d2\qtd\ctfe\Integer.d(164): octal literals 0123 are deprecated, use std.conv.octal!123 instead Are you only testing *D1* versions of QtD? Because that could explain why you're apps are running while mine are not. :)
Jul 20 2011
prev sibling next sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
s/you're/your
Jul 20 2011
prev sibling next sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
Wait wait wait. Sorry this is completely my fault the build script
copied old directories. Sorry for the noise!
Jul 20 2011
prev sibling parent Andrej Mitrovic <andrej.mitrovich gmail.com> writes:
Ok, but the other CTFE issues are still there:

D:\dev\projects\qtd\examples\desktop\systray>dmd -unittest
-version=QtdUnittest -I..\..\..\build_dir\build -I..\..\..\d2
..\..\..\build_dir\build\lib\qtdcore.lib
..\..\..\build_dir\build\lib\qtdgui.lib qrc_systray.d window.d main.d
-ofsystray
..\..\..\d2\qtd\MOC.d(271): Error: gen.output ~= format_ctfe("\x0a //
content:\x0a") cannot be evaluated
at compile time
..\..\..\d2\qtd\MOC.d(272): Error: cannot evaluate format_ctfe("
${},       // revision\x0a",2) at compile time
..\..\..\d2\qtd\MOC.d(484): Error: cannot evaluate generateCode(gen)
at compile time
..\..\..\d2\qtd\MOC.d(513): Error: cannot evaluate generateMetaInfo()
at compile time
..\..\..\d2\qtd\MOC.d(513): Error: argument to mixin must be a string,
not (generateMetaInfo())
Jul 20 2011