Compiling With Windows

[Infernalspawn]

Hi,

im actualy new to the houdini programming stuff, and tried to run the compiler directly from Visual Studio (as i do normaly), but that doesnt work out very well. So i used one batchfile i found,

 hcustom  POP_FrequenzTest.C -I h:\_dev\_libraries\blitz -L h:\_dev\_libraries\blitz

which actualy worked quite well even with other .h & .cpp files which i use for other classes but actualy i got a stupid "unresolved Symbol" message where definitly no every symbol is in place *G*.

So i thought maybe i have to add the other .cpp file to the compiler to get it work.

 hcustom  hou_helper.cpp  POP_FrequenzTest.C -I h:\_dev\_libraries\blitz -L h:\_dev\_libraries\blitz

maybe i dont know, im not realy familar with commandline compiling, seems that i'm screwed without visual studio . thx for your help

Infernalspawn

[Jason]

Hi there,

Sorry I can't be any real help here except to point you to our wiki's page on this: HoudiniDevelopmentKit

Take a look in the FAQ over there...

Good luck,

Jason

[Infernalspawn]

i've read all the stuff but that doesnt realy help me :-(, i guess this is a more general problem not a special houdini question. how do i have to compile an dso/dll without a makefile especialy when i have multiple classes and for every class a seperate cpp/h file ?

pleasssssssssseee help ;-)

thx

Infernal

[Infernalspawn]

yehaaa, hust did it.

there are to ways to compile mutliple classes with hCustom wint windows.

1) Easy Way

Including CPP Files Instead of H files in your Operator C - File

and just compile your Operator C File

2) elegant Way

Compile everything seperatey and link everything by hand, beware of the dependencies

hcustom  hou_intVector.cpp 
hcustom  hou_helper.cpp		   -l hou_intVector.o 
hcustom  hou_gridCube.cpp	-l hou_intVector.o -l hou_helper.o 
hcustom  hou_grid.cpp		-l hou_intVector.o -l hou_helper.o -l hou_gridCube.o 
hcustom  POP_myPOP			-l hou_intVector.o -l hou_helper.o -l hou_gridCube.o -l hou_grid.o

Problem is, everytime you call hcustom it creates a dll file in your dso directory even from the files which are not operators. you still have to delete them

ok maybe it helps somebody

greez Sebastian

[sibarrick]

Cheers! it helps me. I always use the easy way up to now.

I think there's an even more elegant way, but I don't understand it.

If you search this very forum you should come across it....

[edward]

Personally, I would suggest learning how to use makefiles. If you must, there's even an semi-complete nmake file for MSVC provided in $HFS/toolkit/makefiles. Failing that, you can always just make a new project and copy over the compiler/linker options. But I'll refrain from giving step by step instructions because this is really the domain of reading the MSVC (or MSDN) documentation.