<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.lib.boost.build">
    <title>gmane.comp.lib.boost.build</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19875"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19874"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19873"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19872"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19871"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19870"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19869"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19868"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19867"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19866"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19865"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19864"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19863"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19862"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19861"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19860"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19859"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19858"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19857"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.boost.build/19856"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19875">
    <title>Re: {Newbie] linker error 1104 when using VC++ Express</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19875</link>
    <description>AMDG

Bob Keane wrote:

You are building with Visual C++ 9.0, right?

It looks like you installed the libraries for Visual Studio 8.0.

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Steven Watanabe</dc:creator>
    <dc:date>2008-12-03T17:23:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19874">
    <title>Re: Generated header files.</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19874</link>
    <description>
For dependency tracking, it's best if each invocation takes specific input
and produces a single file. Otherwise, Boost.Build or you would have to run
your tool on all files. Here's how to modify my code to make it accept a source:

 make header.h : header_generator input.txt : &lt; at &gt;generate-header ;
 actions generate-header 
{
 $(&gt;[1]) $(&gt;[2]) &gt; $(&lt;)
 }

This assumes that your tool accepts source file as parameter and prints output to stdout.
Note that $(&lt;) is the name of the output file, including directory -- if your tool
always outputs files in the current directory you might want to use this:

 actions generate-header 
{
cd $(&lt;:D)
 $(&gt;[1]) $(&gt;[2]) &gt; $(&lt;:D=)
 }



Using generator, of course, it also possible. But in that case it's best to
have your input files have a specific extensions, so that they can be automatically
processed.

- Volodya
_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Vladimir Prus</dc:creator>
    <dc:date>2008-12-03T17:19:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19873">
    <title>Re: [msvc] defines to turn of security mode</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19873</link>
    <description>
Yes, it does not turn them off.


Sorry, what is your question or suggestion? Above, grammatically, is just
a statement of a fact. I'll be happy with a patch to disable these,
or add a feature disabling this, if msvc users find that useful and agree,
via straw poll or otherwise, on what is needed.

- Volodya
_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Vladimir Prus</dc:creator>
    <dc:date>2008-12-03T17:10:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19872">
    <title>[msvc] defines to turn of security mode</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19872</link>
    <description>Hi,

Am I right that by default the msvc toolset does not turn of this 
security stuff from microsoft?

When I did

nesotto&lt; at &gt;ottosen /cygdrive/d/boost/trunk/tools/build/v2/tools
$ grep -rin "secure" *
intel-win.jam:91:    # Disable Microsoft "secure" overloads in 
Dinkumware librar
ies since they
intel-win.jam:93:    C++FLAGS += -D_SECURE_SCL=0 ;
mpi.jam:250:                &lt;toolset&gt;msvc:&lt;define&gt;_SECURE_SCL=0


there are aparently no flags in the msvc toolset. I have seen other 
pages recomment the following:

"If you use and of the compiled libraries in boost, just add this to 
your bjam command-line:
define=_CRT_NONSTDC_NO_DEPRECATE define=_CRT_SECURE_NO_DEPRECATE 
define=_SECURE_SCL=0 define=_SCL_SECURE_NO_DEPRECATE 
define=_HAS_ITERATOR_DEBUGGING=0"

Thanks in advance

-Thorsten
_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Thorsten Ottosen</dc:creator>
    <dc:date>2008-12-03T17:03:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19871">
    <title>Re: help with v2 build system</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19871</link>
    <description>oh, nice!  it does most of what I need.

I need a rule to fire off before testing.capture-output and I also
need the "generate-xml" rule to go off before RmTemps happens (I guess
I could just disable deleting of the test executables for testcov mode
if it comes to it).

I also have one test that has to link to extra libs when it's linking
shared, so it looks something like

run-test mytest : files files files : : : &lt;link&gt;static ;
run-test mytest : files files files extra libs : : : &lt;link&gt;shared ;

This seems to confuse the rules ("next alternative: required
properties: (empty)")

Thanks.

On 12/2/08, Steven Watanabe &lt;watanabesj&lt; at &gt;gmail.com&gt; wrote:
_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Jonathan Brannan</dc:creator>
    <dc:date>2008-12-03T16:40:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19870">
    <title>Re: Future of Boost.Build?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19870</link>
    <description>_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
</description>
    <dc:creator>Ling Li</dc:creator>
    <dc:date>2008-12-03T16:23:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19869">
    <title>Re: Generated header files.</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19869</link>
    <description>Hello Volodya,

Thanks for your reply.
In fact my 'header generator' uses input files (let's say .txt) which 
are parsed/modified/... to make the corresponding .h files.
Until now, I was launching the generator by hand and it was working on 
all files in the specified directory (as command line parameter).
I suppose I would have to modify it in order to make it take one file at 
a time. Then I could probably generate a list of input files and use 
your piece of script (or try to use the generator from standard module).
Am I in the right way?
Mathias

_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Mathias Lorente</dc:creator>
    <dc:date>2008-12-03T16:09:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19868">
    <title>Re: Boost.Build newbie</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19868</link>
    <description>
Hi Frederic,

I think this is explained in:

http://www.boost.org/boost-build2/doc/html/bbv2/advanced.html

as follows:

Boost.Build actually consists of two parts - Boost.Jam, a build engine with its own
interpreted language, and Boost.Build itself, implemented in Boost.Jam's language.

In C++ Boost tree, tools/jam is the Boost.Jam and tools/build/v2 is Boost.Build. On startup,
Boost.Jam locates Boost.Build files as documented at:


http://www.boost.org/boost-build2/doc/html/bbv2/reference.html#bbv2.reference.general


Yes, that's true. I believe that most build systems require that you explicitly
specify sources. Note that you can use something like:

exe a : [ glob *.cpp ] ;

to save on typing.

- Volodya
</description>
    <dc:creator>Vladimir Prus</dc:creator>
    <dc:date>2008-12-03T15:53:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19867">
    <title>Re: Generated header files.</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19867</link>
    <description>
Hi Mathias,

it's generally best to show what approaches you've tried, so that you
get help about your specific issue, not some approximation. Generally,
something like this should work:


exe header_generator : header_generator.cpp ;
make header.h : header_generator : &lt; at &gt;generate-header ;
actions generate-header 
{
$(&gt;) &gt; $(&lt;)
}
lib header_user : header_user.cpp : &lt;implicit-dependency&gt;header.h ;

- Volodya
_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Vladimir Prus</dc:creator>
    <dc:date>2008-12-03T15:49:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19866">
    <title>Generated header files.</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19866</link>
    <description>Dear list,

I use bjam to build a library which relies on some generated header files.
These files are generated by a specific application which is also built 
using bjam.
I added a dependency for my library so that the application is built 
before the library.
But:
- I didn't manage to launch the application in order to generate the 
necessary header files before the library is being built.

Do you have any hint?
Thanks,
Mathias

_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Mathias Lorente</dc:creator>
    <dc:date>2008-12-03T14:36:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19865">
    <title>Re: Boost.Build newbie</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19865</link>
    <description>


By reference I mean is there anything else than bjam in boost.build? Reading the doc, it seems to me that bjam is the only thing I need for what's called "boost.build". But there is a specific
documentation for boost.build and boost.jam. I am confused with that.



OK for headers, that's great. However, If main.cc #includes a.hh, then if a.cc exists, I need to link main.o with a.o to make the program "main". It seems to me that I have to say to bjam that the
"main" executable target needs a.o. Is that true?



Avis :
Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le
détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes
en tout ou en partie.

Notice:
This message and any attachments are the property </description>
    <dc:creator>frederic.bron&lt; at &gt;alcan.com</dc:creator>
    <dc:date>2008-12-03T14:56:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19864">
    <title>Re: variant propagation</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19864</link>
    <description>
Thank you very much. It was my first look at 'feature' which is indeed 
very powerful.
Cheers, Jan.



_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Jan Boehme</dc:creator>
    <dc:date>2008-12-03T14:27:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19863">
    <title>{Newbie] linker error 1104 when using VC++ Express</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19863</link>
    <description>I am new to boost so bear with me. I used the loader to download and install 
Boost, selected all variants and was sucessful running the example program 
using Visual Studio C++ Express edition. However, when following the first 
tutorial, I get an error, "LINK : fatal error LNK1104: cannot open file 
'libboost_system-vc90-mt-gd-1_36.lib'". I checked previous threads and found 
the one, "[Thread] visual studio hello word multithreading problem" to be 
similar. I looked into the \lib directory for the suspect file but did not find 
it. I did find a lot of libboost_system-vc80... files though, so I suspect 
something is looking for a different version. Is there a simple way to correct 
this? Thanks in advance.

_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Bob Keane</dc:creator>
    <dc:date>2008-12-02T21:42:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19862">
    <title>Re: Dependent install targets</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19862</link>
    <description>
Many thanks for the reply, but I can't get it to work. It seems like 
target(s) defined under project B are somehow referred to from project A(!). 
This is a somewhat edited output from my real project:

C:\users\jni\prj\projectB&gt;bjam -q debug
WARNING: No python installation configured and autoconfiguration
         failed.  See http://www.boost.org/libs/python/doc/building.html
         for configuration instructions or pass --without-python to
         suppress this message and silently skip all Boost.Python target
warning: Python location is not configured
warning: the Boost.Python library won't be built
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
error: Unable to find file or target named
error:     'src/apps/guicli/build//guicli'
error: referred from project at
error:     '/c:/users/jni/prj/projectA'

What is happening here?

"src/apps/guicli/build//guicli" is </description>
    <dc:creator>Johan Nilsson</dc:creator>
    <dc:date>2008-12-03T11:58:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19861">
    <title>Re: Breakage in Doxygen rule</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19861</link>
    <description>
On Windows using 2&gt;

del nofile.txt 2&gt; nul.txt


K
_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Kirit Sælensminde</dc:creator>
    <dc:date>2008-12-03T09:54:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19860">
    <title>Re: Future of Boost.Build?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19860</link>
    <description>
There are actually 3 separate questions:

1. Whether Boost.Build will be continue to be developed
2. Whether Boost.Build be the official build system of C++ Boost
3. Whether Boost.Build will the the only official build system of
C++ Boost.

The answer to (1) is definitely yes -- Boost.Build is fairly
good already, and we're moving ahead nicely. Points (2) and (3) are undecided,
and the actual decision is likely to involve huge number of technical and
political matters.


The roadmap outline at http://www.boost.org/boost-build2/index.html is still
fairly accurate. Milestone 13 is going out really soon now.

- Volodya




_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Vladimir Prus</dc:creator>
    <dc:date>2008-12-03T07:53:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19859">
    <title>Future of Boost.Build?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19859</link>
    <description>_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
</description>
    <dc:creator>Ling Li</dc:creator>
    <dc:date>2008-12-02T20:24:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19858">
    <title>Re: help with v2 build system</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19858</link>
    <description>AMDG

Jonathan Brannan wrote:

Does the attached Jamfile work?

In Christ,
Steven Watanabe

import notfile ;

actions init
{
    echo initializing... &gt;$(&lt;)
}

make initialize : : &lt; at &gt;init ;

all-tests = ;

actions generate-xml
{
   echo Creating xml from $(&gt;) &gt;$(&lt;)
}

variant testcov : debug ;

actions do-nothing
{
}

alias rebuild-in-testcov ;
notfile rebuild-in-testcov : &lt; at &gt;do-nothing : : &lt;variant&gt;testcov ;
explicit rebuild-in-testcov ;

rule run-test ( sources + : args * : input-files * :
                requirements * : target-name ? :
                default-build * )
{
    requirements += &lt;dependency&gt;rebuild-in-testcov ;
    local test = [ run $(sources) : $(args) : $(input-files) :
                   $(requirements) : $(target-name) :
                   $(default-build) ] ;
    local test-name = [ $(test).name ] ;
    make $(test-name).xml : $(test) : &lt; at &gt;generate-xml ;
    all-tests += $(test-name).xml ;
}

run-test a.cpp ;
run-test b.cpp ;

actions generate-html
{
    echo Generating html from $(&gt;) &gt;$(&lt;)
}
</description>
    <dc:creator>Steven Watanabe</dc:creator>
    <dc:date>2008-12-03T01:55:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19857">
    <title>Re: alias rule not propagating requirements?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19857</link>
    <description>AMDG

John Maddock wrote:

Grr.  alias behaves like other main target rules and only propagates 
features that
have the propagated attribute.  This makes non-propagated features 
useless in
the requirements and default-build of an alias target.

You can add the properties like this, I think:

alias type_traits : 
$(boost-root)/libs/type_traits/doc//standalone/$(COMMON_PDF_SETTINGS:J=/) ;


You can use the &lt;name&gt; property.

install pdf : pdf_doc : &lt;name&gt;renamed_pdf.pdf ;

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Steven Watanabe</dc:creator>
    <dc:date>2008-12-03T01:10:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19856">
    <title>Re: Dependent install targets</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19856</link>
    <description>AMDG

Johan Nilsson wrote:

You'll want to override the &lt;location&gt; property.

Project A, Jamfile.jam:

install relocatable-install : a : : &lt;location&gt;/projA/bin ;

Project B, Jamfile.jam:

alias install : /projA//relocatable-install/&lt;location&gt;/projB/bin ;

Note that &lt;location&gt; needs to be in the default-build for
projA//install so that it can be overridden.

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>Steven Watanabe</dc:creator>
    <dc:date>2008-12-02T22:53:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.boost.build/19855">
    <title>Re: Breakage in Doxygen rule</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.boost.build/19855</link>
    <description>
Hmm, on win32 when building the accumulator docs the command is:

del /f /q 
"..\..\..\bin.v2\libs\accumulators\doc\msvc-8.0\debug\threading-multi\statsdoc\*.xml"

and the files get created in:

..\..\..\bin.v2\libs\accumulators\doc\msvc-8.0\debug\threading-multi\statsdoc-xml

Of course we may still be deleting files that haven't been created yet...

John. 

_______________________________________________
Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

</description>
    <dc:creator>John Maddock</dc:creator>
    <dc:date>2008-12-02T19:26:28</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.lib.boost.build">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lib.boost.build</link>
  </textinput>
</rdf:RDF>
