Cannot open include file: 'pthread.h'

[ben-hawkyard-saddington-baynes]

Hello all, I'm encountering difficulties building maya-usd which seem to be similar to those already raised in #27.

I've tried building on windows 7 and on a virtual machine using windows 10. I built pixar usd using visual studio 14 2015 and I've tried building maya-usd using both vs 2015 and vs 2017, on both windows 7 and 10.

I've attached the latest CMakeOutput and CMakeError files as well as the build log. In all permutations of os/vs version I've used the error in CMakeError is the same:

Y:\Users\ben.hawkyard\code\maya-usd\workspace\build\RelWithDebInfo\CMakeFiles\CMakeTmp\CheckIncludeFile.c(1): fatal error C1083: Cannot open include file: 'pthread.h': No such file or directory [Y:\Users\ben.hawkyard\code\maya-usd\workspace\build\RelWithDebInfo\CMakeFiles\CMakeTmp\cmTC_4fb8f.vcxproj]

Thank you for your time!

build_log.txt
CMakeError.log
CMakeOutput.log

[ben-hawkyard-saddington-baynes]

These are the build commands I've been running, too:

For vs 2017

python build.py --maya-location "Y:\Program Files\Autodesk\Maya2018" --pxrusd-location "Y:\Program Files\USD" --devkit-location "Y:\Program Files\Autodesk\Maya2018\devkitBase" --generator "Visual Studio 15 2017 Win64" .\workspace

For vs 2015

python build.py --maya-location "Y:\Program Files\Autodesk\Maya2018" --pxrusd-location "Y:\Program Files\USD" --devkit-location "Y:\Program Files\Autodesk\Maya2018\devkitBase" --generator "Visual Studio 14 2015 Win64" .\workspace

[dtlindsey]

@ben-hawkyard-saddington-baynes
I had the same issue. I ended up having to rebuild USD with Visual Studio 2017, using the
--generator "Visual Studio 14 2015 Win64" argument.
Then I was able to build the maya plugins, change the pathing in the .mod file, and load it successfully in Maya. Give that a shot.

[ben-hawkyard-saddington-baynes]

Hi Daniel, what precisely do you mean by using Visual Studio 2017? Should I open the 2017 Developer command prompt and run the command there?

[dtlindsey]

Yes. Using the 2015 command prompt or a standard cmd didn't work. Thanks, -Daniel On Aug 27, 2019 at 1:35 AM, ben-hawkyard-saddington-baynes < notifications@github.com> wrote: Hi Daniel, what precisely do you mean by using Visual Studio 2017? Should I open the 2017 Developer command prompt and run the command there? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#30?email_source=notifications&email_token=AAXTVXZ57MOFLNJNWTV6JLTQGTRNVA5CNFSM4IPA7H5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5G6ZZQ#issuecomment-525200614>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXTVX4RL6FWLWEZSCN26A3QGTRNVANCNFSM4IPA7H5A> .

[ZhongLingXiao]

Hi

I have change file : maya-usd\plugin\al\usdtransaction\AL\usd\transaction\tests\CMakeLists.txt
line 52 from

set_tests_properties(${USDTRANSACTION_PYTHON_TEST_NAME} PROPERTIES ENVIRONMENT PYTHONPATH=${CMAKE_BINARY_DIR}/${INSTALL_DIR_SUFFIX}/usdtransaction:${CMAKE_BINARY_DIR}/src:$ENV{PYTHONPATH} )

to
set_tests_properties(${USDTRANSACTION_PYTHON_TEST_NAME} PROPERTIES ENVIRONMENT "PYTHONPATH=${CMAKE_BINARY_DIR}/${INSTALL_DIR_SUFFIX}/usdtransaction:${CMAKE_BINARY_DIR}/src:$ENV{PYTHONPATH}" )

which only add "" for the parameter and the problem solved

[samkenw]

@ZhongLingXiao This resolved the issue for me, thank you!

[fowlertADSK]

I believe this was finally fixed properly as part of a recent change to get the AL unit tests running on all platforms. See: #198