CodeBreak Posted July 31, 2009 Share Posted July 31, 2009 Alright, yes. Everything is installed. Visual Studio and HDK 10.0. All I need how to and I'll be on my way to doing this. If anyone does have experience working with compiling for Houdini on Windows, help me out. I can get this done a lot faster with visual aid instead of reading a ton of pages. That's how I learn. Quote Link to comment Share on other sites More sharing options...
edward Posted August 1, 2009 Share Posted August 1, 2009 HDKFrequentlyAskedQuestions Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 4, 2009 Share Posted August 4, 2009 (edited) Hey guys, I'm trying VERY hard to follow the instructions on here (HDK Frequently Asked Questions), but I'm not able to make the test go well. I'm thinking my environment variables may be set wrong and since I have a different version than what they're talking about...I need a bit of help. The system settings I have are as follows (Let me know if they're wrong, and how to fix them PLEASE): MSVCDir is set to "C:/Program Files (x86)/Microsoft Visual Studio 9.0/Common7/IDE/VC". Is this right? I don't EXACTLY understand the part that says "Also make sure that your Visual C++ installation is included in your PATH environment variable. Following the example above, you need to add ["c:/vstudio8/VC/bin";"c:/vstudio8/Common7/Tools/bin";"c:/vstudio8/Common7/IDE"]" The only thing related to the Visual Studio installation that I can see in the EV panel is VS90COMNTOOLS - C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Tools\ I think they're wrong because: When I type "csh", I get a "%" symbol upon pressing enter. When I type in "cd $HT/samples/SOP" I receive a message saying "The system cannot find the specified path" When I type"hcustom SOP_Star.C", it seems to compile something...but when I start Houdini, press TAB and start to type "Star", Star isn't coming up. I'm using Windows Vista Ultimate x64, Houdini 10.0 x64 build 295, and Visual Studio 2008. Edited August 4, 2009 by CodeBreak Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted August 4, 2009 Share Posted August 4, 2009 Hi there, Let me see if I can help, though I don't have a Vista machine, I have been compiling with MS .Net 2003 for a number of years, but I also am now having problems after upgrading to VC8. In my previous configuration (which worked well) I only had to set the MSVCDir variable, didn't have to manually edit the path variable. Now, after installing VC8 and setting everything as per the procedures, hcustom starts to run but then quits with no error messages and no code compiled. I haven't gotten around to looking over the hcustom script to see what's going on, I'm assuming it's in my config. However, there's a few things you have confused, let's see if we can sort it out. Try this: 1) Open up the "Command Line Tools" from your Houdini installation. The first lines of text in the shell should say something like: Welcome to the Houdini 9.5.379 command line tools. The Houdini environment has been initialized. [windows-i686-cl13] Starting command prompt... Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. 2) From this shell, type in "hcustom", you should get a usage statement. This verifies that all your Houdini related vars are (probably) correct. 3) type "csh" (you're now running the csh shell from the Houdini distro) 4) type "cd $HT" (you should now be in the HDK toolkit directory) 5) type "cd samples/SOP/" (now you're in the HDK SOP samples directory) 6) type "hcustom SOP_Star.C" If the compiler is installed and the env vars are correct, it will build the SOP_Star.dll and place in in home houdini10.0/dso/ directory. (make sure your home houdini10.0/dso/ directory has been created before compiling). Let me know how that works out. Hope that helps a bit. Mark Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 4, 2009 Share Posted August 4, 2009 Ok. After typing "hcustom", I get a message saying "The MSVDir evironment variable is set, but does not point to a valid directory. Please set it correctly and try again" What am I doing wrong with the path of the variable? Should it be pointing to JUST the base installation "C:\Program Files (x86)\Microsoft Visual Studio 9.0", or does it need to point somewhere more specific inside of that directory? Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted August 4, 2009 Share Posted August 4, 2009 I believe it should be pointing into the directory, e.g.: C:/PROGRA~1/MICROS~1.0/VC Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 4, 2009 Share Posted August 4, 2009 Ok I fixed that problem. The path has to be to the base installation. I followed all of the steps, and here's what happened in the cmd: Welcome to the Houdini 10.0.295 command line tools. The Houdini environment has been initialized. [windows-x86_64-cl14] Starting command prompt... Microsoft Windows [Version 6.0.6002] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Users\Brandon>hcustom Usage: hcustom [-g] [-s] [-t] [-L libdir] [-I incdir] [-l libname] [-i dir] source_files This program will make custom plug-ins (DSO's) for Houdini. NOTE: The hdkinstall program must be run before this command can be used for the first time. Options: -d Display CFLAGS environment variable passed to hcompile -g Create debug version of the DSO -e Echo the commands run by this program -i dir Specify an install directory (default HOME\houdini10.0\dso) -s Create a stand alone application instead of a DSO -l libname Link with the library named libname; libraries are passed to the compiler in the order in which they are given -L libdir Add libdir to the library file search path -I incdir Add incdir to the include file search path -t Turn off creation of tagging information. At least one object file in an archive must have the tagging information for Houdini to load the .dll successfully C:\Users\Brandon>csh %cd $HT %cd samples/SOP/ %hcustom SOP_Star.C Making 'SOP_Star.o' and 'C:/Users/Brandon/houdini10.0/dso\SOP_Star.dll' from 'SO P_Star.C' Failed to run C:\Program with error 2: The system cannot find the file specified . Argument list: 0: C:\Program 1: Files 2: (x86)\Microsoft 3: Visual 4: Studio 5: 9.0\VC\bin\amd64\cl 6: -TP 7: SOP_Star.C 8: -DUT_DSO_TAGINFO="3262197cbf305b152da202866708a0c82e45c1b0917c87ce10f99048 5e46e4887b912bda9f321d610646ccfd20da21084bffe20afdd5e35544162fe867f3abac5bbe45a0 ff924994e17f970847d843bde50a9abee5" 9: -TP 10: -Zc:forScope 11: -DVERSION=10.0.295 12: -DI386 13: -DWIN32 14: -DSWAP_BITFIELDS 15: -DDLLEXPORT=__declspec(dllexport) 16: -I 17: . 18: -I 19: C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/include 20: -I 21: C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/PlatformSDK/include 22: -I 23: C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/toolkit/include/htools 24: -I 25: C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/toolkit/include 26: -Ox 27: -MD 28: -EHsc 29: -GR 30: -DSESI_LITTLE_ENDIAN 31: -DMAKING_DSO 32: -FoSOP_Star.o 33: -LD 34: -link 35: /libpath:C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/lib/amd64 36: /libpath:C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC/PlatformSDK /lib/amd64 37: C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/*.a 38: C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/*.lib 39: -out:C:/Users/Brandon/houdini10.0/dso/SOP_Star.dll But then after all of this I checked the dso directory............and nothing was there. I am so lost. Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted August 4, 2009 Share Posted August 4, 2009 There's something going with the white spaces in the path to cl. If you look at the argument list, hcustom is trying to parse out the path to cl as separate arguments. Is your MSVCDir var set in the "8.3" format? Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 4, 2009 Share Posted August 4, 2009 There's something going with the white spaces in the path to cl. If you look at the argument list, hcustom is trying to parse out the path to cl as separate arguments. Is your MSVCDir var set in the "8.3" format? I'm not quite sure. Under my System Variables, it looks like this: Variable Name: MSVCDir Variable Value: C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted August 4, 2009 Share Posted August 4, 2009 Yea, that's a problem. Use the "dir /x" command to find the 8.3 format path of the VC8 install (do this before running csh). Go up to the root of your drive that you have Houdini installed, and run "dir /x" to see the directory contents in both formats, long and 8.3, then cd into each directory, note the 8.3 dir name for each component of the path until you reach the destination ... Isn't WINDOZE fun???? Um, don't think so! Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 4, 2009 Share Posted August 4, 2009 Yea, that's a problem. Use the "dir /x" command to find the 8.3 format path of the VC8 install (do this before running csh). Go up to the root of your drive that you have Houdini installed, and run "dir /x" to see the directory contents in both formats, long and 8.3, then cd into each directory, note the 8.3 dir name for each component of the path until you reach the destination ... Isn't WINDOZE fun???? Um, don't think so! Ok I got the value "c:\PROGRA~2\MICROS~1.0\VC". So I'm supposed to put this in place of "C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC" in the Environment Variable dialog, right? Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted August 4, 2009 Share Posted August 4, 2009 Ok I got the value "c:\PROGRA~2\MICROS~1.0\VC". So I'm supposed to put this in place of "C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC" in the Environment Variable dialog, right? Yes Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 4, 2009 Share Posted August 4, 2009 OMG xionmark I forgot to install the 64-bit compiler tools. Let me do that, try again, and then I'll get back to you. Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 4, 2009 Share Posted August 4, 2009 Ok now I'm getting this: C:\Users\Brandon>csh %cd $HT/samples/SOP %hcustom SOP_Star.C Making 'SOP_Star.o' and 'C:/Users/Brandon/houdini10.0/dso\SOP_Star.dll' from 'SO P_Star.C' Microsoft ® C/C++ Optimizing Compiler Version 15.00.30729.01 for x64 Copyright © Microsoft Corporation. All rights reserved. SOP_Star.C Unknown compiler version - please run the configure tests and report the results Microsoft ® Incremental Linker Version 9.00.30729.01 Copyright © Microsoft Corporation. All rights reserved. /out:SOP_Star.dll /dll /implib:SOP_Star.lib /libpath:c:/PROGRA~2/MICROS~1.0/VC/lib/amd64 /libpath:c:/PROGRA~2/MICROS~1.0/VC/PlatformSDK/lib/amd64 C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libarray.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libAU.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libBM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libBR.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libBV.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCH.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCHOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCHOPNET.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCHOPZ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCHUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCL.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCLO.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCMD.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCOP2.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCOPNET.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCOPZ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCPUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libCVEX.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libDAE.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libDD.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libDM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libDOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libDOPZ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libdxf.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libEXPR.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libFBX.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libFS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libFUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libFUSE.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGAS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGB.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGD.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGDT.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGEO.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGQ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGR.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGR2D.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGU.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libGVEX.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libHOM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libHOMF.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIFD.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIMG.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIMG3D.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIMGUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIMH.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIMP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIMS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libIPR.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libJEDI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libJIVE.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libjpeg.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libKIN.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libLA.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libLM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMATUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMC.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMCS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMDS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMGR.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMH.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMIDI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMOT.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMPI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMPS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMSS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMT.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMV.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libMWS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libOBJ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libOH.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libOP3D.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libopenexrh.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libOPUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libpaudio.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPBR.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libpngh.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPOPNET.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPOPUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPOPZ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPRM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPSI2.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPXL.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libPY.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libRBD.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libRE.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libROP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libRU.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSHLF.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSHOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSIM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSIMZ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSOHO.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSOPZ.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libSYS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libTAKE.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libTBF.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libTHOR.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libtiff.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libTIL.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libtools.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libTS.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libUI.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libUT.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libVEX.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libVM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libVMAT.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libVOP.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libVOPNET.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libVPRM.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libVRAY.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libWIRE.a C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/audiere.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/audiere_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/boost_thread-vc80-mt-1_3 3_1.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/boost_thread-vc80-mt-gd- 1_33_1.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/fbxsdk_md.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/fbxsdk_md_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libasprintf.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libasprintf_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libcharset.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libcharset_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libglib-2.0.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libglib-2.0_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libglibmm-2.4.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libglibmm-2.4_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libgmodule-2.0.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libgmodule-2.0_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libgobject-2.0.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libgobject-2.0_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libgthread-2.0.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libgthread-2.0_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libiconv.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libiconv_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libintl.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libintl_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libsigc-2.0.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libsigc-2.0_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libsndfile.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libsndfile_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libxml++-2.6.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libxml++-2.6_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libxml2.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/libxml2_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/python25.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/python25_d.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/zdll.lib C:/PROGRA~1/SIDEEF~1/HOUDIN~1.295/custom/houdini/dsolib/zdll_d.lib -out:C:/Users/Brandon/houdini10.0/dso/SOP_Star.dll SOP_Star.o LINK : fatal error LNK1104: cannot open file 'kernel32.lib' Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted August 4, 2009 Share Posted August 4, 2009 Well you're almost there. I assume the warning you're getting is related to hcustom trying to link to a 32 bit DLL. Unfortunately, this is just about as far as I can help, I'm a UNIX programmer and don't touch WIN machines except to do cross compiles, so it would likely take me a while to dig into this one. Someone at SESI should be able to identify this? Or maybe Steven Ong? Or Edward? Any of you windows guys got an idea on this one? Quote Link to comment Share on other sites More sharing options...
eloop Posted August 5, 2009 Share Posted August 5, 2009 (edited) Codebreak, don't forget that you should be using VC8 (Visual Studio 2005) not VC9 (Visual Studio 2008). You probably can't build HDK tools with VC9. You're beginning to get an idea why Mark and I stay away from Windows... At one stage you had to use a version of Visual Studio that couldn't be purchased any more. -Drew Well you're almost there. I assume the warning you're getting is related to hcustom trying to link to a 32 bit DLL. Unfortunately, this is just about as far as I can help, I'm a UNIX programmer and don't touch WIN machines except to do cross compiles, so it would likely take me a while to dig into this one. Someone at SESI should be able to identify this? Or maybe Steven Ong? Or Edward? Any of you windows guys got an idea on this one? Edited August 5, 2009 by eloop Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 5, 2009 Share Posted August 5, 2009 Darnit! So I'm guessing this is an easy breezy solution on....Linux? Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 5, 2009 Share Posted August 5, 2009 Ok I got a hold of Visual Studio 2005. I did the test compile and everything went well, no errors. It built the .dll. Not sure exactly how to call it up in Houdini however. I tried TAB and the typing star, but it didn't show anything. Anyone got any advice before I try to compile the HOT? Quote Link to comment Share on other sites More sharing options...
eloop Posted August 5, 2009 Share Posted August 5, 2009 Ok I got a hold of Visual Studio 2005. I did the test compile and everything went well, no errors. It built the .dll. Not sure exactly how to call it up in Houdini however. I tried TAB and the typing star, but it didn't show anything. Anyone got any advice before I try to compile the HOT? Are you hitting TAB in the Surface/SOP context ? Advice - good luck Actually look at the recent thread with phong. -Drew Quote Link to comment Share on other sites More sharing options...
CodeBreak Posted August 5, 2009 Share Posted August 5, 2009 Thanks. Took a look at the phong thread, but it didn't help much because I can't even get that far. When I cd into the scr directory, and then type: .\compile_win64.sh I get this dialog popping up asking me what program to open compile_win64.sh with. I'm sure I'm doing something wrong yet again. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.