Jordan,

Also, be aware that not all versions of Visual Studio are appropriate for Nuke 
Plugin Development.  Unless you are very familiar with VS, I would recommend 
starting only with VS 2005 (v.8).  If you look in your C:/Program Files/ Nuke 
6.XvY/Documentation folder, you'll see a 'vc8' folder  in there.  It is an 
example visual studio solution that is guaranteed to work.  What I do to set up 
a new VS solution is copy the entire directory, and then basically do a global 
search and replace in all the contained files (including the .sln and .vcproj 
files), replacing the old 'Example' plugin name with my new one.  Then you are 
guaranteed to have everything set correctly.

For new users, VS 2008 and VS 2010 are not recommended, in my humble opinion.  
Although, as a tip, if you have both VS 2005 and VS 2010, the 'Daffodil' plugin 
(http://visualstudiogallery.msdn.microsoft.com/da1f2443-624b-43b7-8480-b092b2962843)
 has been proved to be extremely useful for me.  It permits you to compile 
using the 2005 compiling environment while taking advantage of the much more 
advanced 2010 IDE.

Hope that helps a bit!

Steve

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Sebastian Elsner
Sent: Wednesday, April 04, 2012 12:48 AM
To: Nuke plug-in development discussion
Subject: Re: [Nuke-dev] newbie question compiling example plugin

Adding the path alone is not enough. You have to add the lib name to the 
Additional Library dependencies. See the example workspace which comes with 
nuke or follow my article on nukepedia: 
http://www.nukepedia.com/written-tutorials/developing-nuke-plugins-on-windows/

Cheers

Sebastian

On 04/04/2012 09:40 AM, Jordan Olson wrote:
> Hi guys!
> I'm attempting to compile my first (the example) plugin using 
> Microsoft Visual Studio. Although I've added the /include directory to 
> the linker input options of the project properties, I'm still getting 
> the following error when trying to compile.
>
> LINK : fatal error LNK1104: cannot open file 'DDImage.lib'
>
> Seems very simple? How would you set up your project to ensure the 
> compiler can find the DDImage libraries?
> cheers,
> Jordan
> _______________________________________________
> Nuke-dev mailing list
> [email protected], http://forums.thefoundry.co.uk/ 
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev


-- 
Sebastian Elsner    -    pipeline td   -   r i s e |  fx

t:  +49 30 20180300                 [email protected]
                                           www.risefx.com

r i s e |  fx  GmbH
Schlesische Strasse 28 Aufgang B, 10997 Berlin
Geschäftsführer: Sven Pannicke, Robert Pinnow

Handelsregister Berlin HRB 106667 B

_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/ 
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
(CONFIDENTIALITY NOTICE: The information contained in this email may be 
confidential and/or privileged. This email is intended to be reviewed by only 
the individual or organization named above. If you are not the intended 
recipient, or an authorized representative of the intended recipient, you are 
hereby notified that any review, dissemination or copying of this email, or the 
information contained herein is strictly prohibited. If you have received this 
communication in error, please notify the sender by return email and delete 
this email from your system. Thank You.)

_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev

Reply via email to