TFS and library path

Question

Hi!

We are using TFS 2010 and build agent/controller, default template.

The problem is that when the compiler shall link the libraris it is missing a directory in the path. TFS use Source directory for source code and Binaries directory for the binary application. At link the compiler is stepping on step back (../) but insted of write the path as: Source\Project\Configurationtype\ its writing it as  Project\Configurationtype\ .

The application is compiled with out any problem locally.

Im new to TFS build so any tip is welcomed.

Answer 1

Hi Natgel,

Thanks for your post!

Please refer to http://stackoverflow.com/questions/2655879/tfs-build-server-cannot-find-assembly-reference for the assembly reference for the Team Build 2010.

For more information, you can refer to http://msdn.microsoft.com/en-us/library/e74a18c4.aspx

Hope it helps!

Best Regards,

---

Cathy Kong [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Hi

The problem is that the "build in" path in ths build( i guess that they are coming from the build process template) are pointing wrong. By adding the binaries directory but not adding the source directory, those two directories(Binary and Source) are TFS doing. So my quiestion where can i change them?

Exemple:

D:\Build\1\soulution\buildtype\binaries\\..\project\configurationtyep\file.res

Should be

D:\Build\1\solution\buildtype\binaries\\..\source\project\configurationtype\file.res 

Small different but huge effekt.

Any tips?

Answer 3

Hi Natgel,

Thanks for your feedback!

The "build in" path in the build is configured in the Working Directory of the Build Agent, you can perform the following steps to changed it:

1. Open the Team Foundation Server Administration Console,
2. select Build Configuration,
3. click Properties of the build agent which you want to use,
4. In the Build Agent Properties dialog, in the Working Direcory, you can change it to your own path.

Hope it helps!

Best Regards,

---

Cathy Kong [MSFT]
MSDN Community Support | Feedback to us

Answer 4

Hi!

The answer wasnt there, it was hiding in how c++ project file are build but thanks anyway!

Answer 5

Hi Natgel,

Thanks for your feedback!

We will be appreciated if you can share the solution here, which will be benefit to other community members having the similar issue.

Best Regards,

---

Cathy Kong [MSFT]
MSDN Community Support | Feedback to us

Answer 6

Hi!

I found that the problem was at the definition of the Output Directory. In my case i hade change the macro from $(ProjectDir) (that fit the local compile) to the $(SolutionDir) macro that fit the build server.

/Natan