windows buildscript #27
Labels
Comments
|
For starters I would probably try removing the deps\oce\build-vs2013-x64 folder and try again. If that doesn't help, maybe try removing deps\oce altogether and rerun the script. |
|
Thanks for your help. Tested both, same problem. |
|
@Stinkfist0 I don't see any recent commits in OCE (not sure if recent changes broke the oce build), but maybe it's better to let the build script checkout a tag to be sure it's stable? |
|
@aothms Yeah, it would be nice to fix OpenCOLLADA and Open Cascade to known good revisions. |
+1 |
|
I will be testing with VS 2013 x64 build on Windows 10 and will report back. |
|
@berndhahnebach seems to build OK. Maybe try building the INSTALL project of the oce.sln manually from the VS IDE? |
|
I'm not a windows guy in the regard of compiling. How would I do this? |
|
@berndhahnebach A-haa, I see |
|
The window title of my comand prompt says Thats the one I have been successfully build IfcOpenShell and depencies with your Build script quite a few times since August 2015 |
|
OK, there might be something wonky in OCE regarding that. I'd recommend using Developer Command Prompt for VS2013 if doing only 32-bit builds or VS2013 x64 Native Tools Command Prompt if doing 64-bit and 32-bit builds. Just to make sure: you are running on a 64-bit Windows? |
|
deleted all and started new .... Win7 Pro SP1, all Windows updates C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts\Developer Command Prompt for VS2013 EDIT: sorry but I do not know how to change languarge on a windows command promt to english. I do not even know it it is possible though. |
|
It would appear that you're using Express instead of Community, but don't think that should matter. Note that with Developer Command Prompt for VS2013 you want/can build 32-bit version, i.e. pass "Visual Studio 12 2013" (omit the Win64). FYI, in the near future I'm committing an enhancement which picks the used generator automatically. You might want to translate "Das Sprungziel - InstallCMakeProject wurde nicht gefunden." into English and Google that. System languages can be added and changed from Control Panel\Clock, Language, and Region\Language |
|
To build the install INSTALL project manually: after using the right CMake generator and assuming the build still fails, open up C:\Users\bhb\Desktop\ifcos\ifcosdev\deps\oce\build-vs2013-x86\OCE.sln, in the Solution Explorer you should see INSTALL project, right click -> project only -> build INSTALL only |
No I don't see any "INSTALL project" to do a right click on. I used "ALL_BUILD" instead. Means I made right click --> build only ALL_BUILD. In output window it said. I tried rebuild and right click on ALL_BUILD --> clean only ALL_BUILD and build no sucess same output. BTW: Thanks very much for all the help so far. |
|
Did you now switch to x64 command prompt? Please tell exactly which command prompt (and toolset thereof) and CMake generator you are using. INSTALL should be under the CMakePredefinedTargets folder. Also, can you try putting |
|
|
How about the CMake generator? For you it must be "Visual Studio 12 2013". Weird that you don't have the VS2013 x64 Native Tools Command Prompt shortcut there. Maybe it's a limitation in the Express edition (Community is really what's recommended), maybe you forgot the check some box during the installation, who knows. And just making sure that you are running 64-bit Windows (Win+Pause will tell that quickly, see System type)? Although judging from the Program Files folder that is the case. |
|
Deinstalled express edition and installed community edition ... Just to make sure I'm using the right tools .... Win+Pause --> 64 bit From: Same problem as before. I wil try the manual build of oce. |
|
OK, this would appear to be a very weird bug indeed. BTW what's your CMake version ( |
|
C:\Users\bhb\Desktop\ifcos\ifcosdev\win>cmake --version CMake suite maintained and supported by Kitware (kitware.com/cmake). C:\Users\bhb\Desktop\ifcos\ifcosdev\win> |
|
OK, it might be worth a shot to update CMake, although it should not be issue here, but who knows... |
|
Also the output from OCE's CMake invokation would be interesting too see (put |
done
|
|
And again the error I get. Slowly I understand more of build processes on windows os. Compiling has been done successful ("Der Buildvorgang wurde erfolgreich ausgeführt.") , but installation does not work due to a not valid directory name ("Der Verzeichnisname ist ungültig."). But the directory name is not printed ? |
|
I'm getting closer ...
|
|
Remember to switch to RelWithDebInfo build type from the menu (a freshly created sln by CMake defaults to Debug) |
|
|
Does the trick inside MS VS 2013
How do I continue the build script or find where the culprit in the script is ? |
|
Great to hear that at least a manual workaround has been found. |
|
Yeah not possible without your help! How do I continue the build script ? |
|
Errors about commands "b" and "1" seem really strange. Maybe this is some weird locale specific bug regarding batch files. I would probably try first changing the OS language to English, |
|
You could also try putting |
wired things ... It breaks before even begin to start oce stuff ... before even start OpenCollada |
|
Just tried a clean build with latest master branch, which is commit 480 (90f72c4) and it builds like a charm on windows !!! again thanks for all the afford you did stinkfist ! |
|
Great to hear! @aothms I think this could be closed now. |
|
Done. Thanks both for the extensive debugging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just tried to build on windows 7 by provided buildscript. I had done this before sucessfully a few times (last one on 8th of January). I get an error on building depencieces. I do not know if it is the right place to report the problem?
Attached a file containing the last 9999 lines of compiling. Is oce the culprit?
bernd
log.txt
The text was updated successfully, but these errors were encountered: