Moving CodeJock Source

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   We have a system wherein we develop multiple versions of the same application at the same time (a bugfix version and a feature-rich version).  The two, in some cases, use different versions of CodeJock and so we've had to move the CodeJock source library to someplace within each project's hierarchy.  Then we point each project to the new location.  This works well except for one problem.  It seems that no matter how I setup the include directories, I consistently get a link error (when resources are being built) saying that the file "XTToolkitPro.rc" could not be found. This line is the one causing the problem:

#include "XTToolkitPro.rc"

And it's in our own project's .rc2 file.  When I change the path in the #include to a relative one leading directly to the file as in:

#include "../xtreme/XTToolkitPro.rc"

It finds that file then has problems with finding files in subsequently included resource files such as:

XTP_IDC_HSPLITBAR CURSOR  DISCARDABLE  "Common/res/splith.cur"

Inside the file "Common/Resource.rc"

I've had to fix the problem by adding the path to the new xttoolkitpro location in the VS build paths options dialog, but that's exactly what I wanted to get away from.  Does anyone have any suggestions?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
k_shehadeh Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 19 August 2005 Location: United States Status: Offline Points: 10	Post Options Post Reply Quote k_shehadeh Report Post Thanks(0) Quote Reply Topic: Moving CodeJock Source Posted: 17 October 2005 at 7:19am
	We have a system wherein we develop multiple versions of the same application at the same time (a bugfix version and a feature-rich version). The two, in some cases, use different versions of CodeJock and so we've had to move the CodeJock source library to someplace within each project's hierarchy. Then we point each project to the new location. This works well except for one problem. It seems that no matter how I setup the include directories, I consistently get a link error (when resources are being built) saying that the file "XTToolkitPro.rc" could not be found. This line is the one causing the problem: #include "XTToolkitPro.rc" And it's in our own project's .rc2 file. When I change the path in the #include to a relative one leading directly to the file as in: #include "../xtreme/XTToolkitPro.rc" It finds that file then has problems with finding files in subsequently included resource files such as: XTP_IDC_HSPLITBAR CURSOR DISCARDABLE "Common/res/splith.cur" Inside the file "Common/Resource.rc" I've had to fix the problem by adding the path to the new xttoolkitpro location in the VS build paths options dialog, but that's exactly what I wanted to get away from. Does anyone have any suggestions?
	Karim Shehadeh iWonder Designs http://www.iwonderdesigns.com

Barto Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 27 February 2005 Location: Germany Status: Offline Points: 60	Post Options Post Reply Quote Barto Report Post Thanks(0) Quote Reply Posted: 17 October 2005 at 5:04pm
	check in visual studio project settings under resources, there is a line where you can specifiy search paths like for includes. I used that and then you don't have to change anything in the resources.

k_shehadeh Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 19 August 2005 Location: United States Status: Offline Points: 10	Post Options Post Reply Quote k_shehadeh Report Post Thanks(0) Quote Reply Posted: 19 October 2005 at 5:57am
	Thank you! That did the trick.
	Karim Shehadeh iWonder Designs http://www.iwonderdesigns.com