Build/Incorporation issues

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Follow "Using HadesMem" instructions in html format

What is the expected output? What do you see instead?
The library gets linked against, and necessary header-containing directories 
are brought into the search domain.

Instead, the boost build system yields a vague error:
error: Unable to find file or target named
error:     '/HadesMem//Memory'
error: referred from project at
error:     'Projects/Injector'

(The boost build system debug levels are far too granular and make it difficult 
to track down.)

My jamfile contained:

#/Projects/Injector/Jamfile
use-project /HadesMem
  :  ../../../../HadesMem
  ;

exe Injector
  :  Source/Injector.cpp
     /HadesMem//Memory #Fails to be discovered
  ;

Upon ignoring the documentation and fixing my jamfile to the best of my 
abilities, my jamfile looks like this:

#/Projects/Injector/Jamfile
use-project /HadesMem
  :  ../../../../HadesMem
  ;

exe Injector
  :  Source/Injector.cpp
     /HadesMem//Src/Memory
  ;

At this stage, boost build tries to rebuild the boost libraries, and fails:

compile-c-c++ 
..\..\HadesMem\Src\Dependencies\Boost\bin.v2\libs\date_time\build\m
svc-10.0\release\link-static\threading-multi\gregorian\greg_month.obj
greg_month.cpp
..\..\HadesMem\Src\Dependencies\Boost\libs\date_time\src\gregorian\greg_month.cp
p
(111) : error C2220: warning treated as error - no 'object' file generated
..\..\HadesMem\Src\Dependencies\Boost\libs\date_time\src\gregorian\greg_month.cp
p
(111) : warning C4100: 'type' : unreferenced formal parameter
..\..\HadesMem\Src\Dependencies\Boost\libs\date_time\src\gregorian\greg_month.cp
p
(124) : warning C4100: 'type' : unreferenced formal parameter
..\..\HadesMem\Src\Dependencies\Boost\libs\date_time\src\gregorian\greg_month.cp
p
(142) : warning C4100: 'type' : unreferenced formal parameter
..\..\HadesMem\Src\Dependencies\Boost\libs\date_time\src\gregorian\greg_month.cp
p
(155) : warning C4100: 'type' : unreferenced formal parameter

Figuring that a pedantic directive was being propagated, I patched 
Src/Memory/Jamfile.v2 line 8 and allowed warnings to be warnings.
Now everything compiles fine - but it was a huge waste of time for me. (><)

All that aside, thanks for working on this otherwise sweet-ass library and 
making it publicly available.

Original issue reported on code.google.com by teissler...@gmail.com on 31 Aug 2011 at 5:11

[GoogleCodeExporter]

Thanks for reporting this. I'm about to go out, but I will have a look when I 
get home tonight.

Hopefully it should just be a matter of slightly tweaking the Jamfiles. I'll 
set up a test project and upload it somewhere as an example once I fix 
everything.

Thanks again. (Especially for giving such a detailed report.)

Original comment by raptorfactor@raptorfactor.com on 31 Aug 2011 at 5:15

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Hey, I haven't forgotten about this, just been having a busy week. Will get 
around to this ASAP.

Original comment by raptorfactor@raptorfactor.com on 1 Sep 2011 at 8:06

[GoogleCodeExporter]

Thanks for the rapid replies, take your time.

Original comment by teissler...@gmail.com on 1 Sep 2011 at 9:36

[GoogleCodeExporter]

From giving this a closer look it seems I may need to muck around with the 
build system a bit more in order to make the 'experience' more enjoyable.

I've added it to the list of changes I want completed before I release v1.5.0. 
Will hopefully fix it this week.

Thanks again.

Original comment by raptorfactor@raptorfactor.com on 4 Sep 2011 at 3:00

• Added labels: Maintainability, Milestone-Release1.5, Usability

[GoogleCodeExporter]

Original comment by raptorfactor@raptorfactor.com on 4 Sep 2011 at 3:00

• Changed state: Started

[GoogleCodeExporter]

Ugh. The more I use Boost.Build, the more it makes me want to change to CMake. 
:P

Original comment by raptorfactor@raptorfactor.com on 8 Sep 2011 at 6:12

[GoogleCodeExporter]

Fixed in r1485. Please read the Building section of the docs again and confirm 
that the new process works for you, there are minor changes/clarifications to 
the process, and a name change to the library you link to. Thanks. :)

Original comment by raptorfactor@raptorfactor.com on 28 Sep 2011 at 9:01

• Changed state: Fixed