# Build target for YAML project

**URL:** <https://www.ruby-forum.com/t/build-target-for-yaml-project/139211>\
**Category:** IronRuby\
**Created:** [June 1, 2008, 10:22pm UTC](https://www.ruby-forum.com/t/build-target-for-yaml-project/139211 "2008-06-01T22:22:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bwinborg](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/51bf81/32.png) [@bwinborg](https://www.ruby-forum.com/u/bwinborg)\
**Post date:** [June 1, 2008, 10:22pm UTC](https://www.ruby-forum.com/t/build-target-for-yaml-project/139211/1 "2008-06-01T22:22:03Z")

</div>

Is there a reason why the output path for the YAML project is:

```
..\..\..\..\..\Main\bin\Debug\

```

rather than

```
..\..\build\debug\

```

? The latter tries to place binaries outside the checkout folder.

---

<div class="post-metadata">

**Author:** ![bwinborg](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/51bf81/32.png) [@bwinborg](https://www.ruby-forum.com/u/bwinborg)\
**Post date:** [June 1, 2008, 11:14pm UTC](https://www.ruby-forum.com/t/build-target-for-yaml-project/139211/2 "2008-06-01T23:14:20Z")

</div>

The reason for this is that our internal directory tree doesn’t quite  
match  
the tree that gets published to RubyForge. The process for pushing out  
the  
sources includes the application of some transforms to file layout and  
to  
certain files. This file was apparently missed, probably because it was  
added during the run-up to RailsConf. The best way to make sure it gets  
resolved is to file a bug report for it at RubyForge.