Many lingering v1 dependencies

I keep seeing BBv1 dependencies in our supposedly-v2
scripts,
Jamfiles, and documentation.  For example
$BOOST_ROOT/Jamfile.v2 uses
the --with-python-root option to set the PYTHON_ROOT
variable, which
has no effect in v2.  $BOOST_ROOT/configure isn't designed
to work
with BBv2 it seems.
http://www.boost-consulting.com/boost/more/s
eparate_compilation.html
still needs to be updated for BBv2.  I'm concerned that many
more
instances of this problem may exist, and I'm not sure how to
resolve
them.  Is there a reasonable automated search we could use?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

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

On Sunday 10 December 2006 15:33, David Abrahams wrote:
> I keep seeing BBv1 dependencies in our supposedly-v2
scripts,
> Jamfiles, and documentation.  For example
$BOOST_ROOT/Jamfile.v2 uses
> the --with-python-root option to set the PYTHON_ROOT
variable, which
> has no effect in v2.  

FWIW, I stumbled upon this problem half a year ago (cf.  
http://tinyurl.com/y5x567). Later I discovered that it's being tracked by 
this ticket:

h
ttps://zigzag.cs.msu.su:7813/boost.build/ticket/61

I recently tried to make the --with-python-[root/version]
options work, but 
don't quite know how to override a default
python-configuration residing in 
user-config.jam.

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

On Sunday 10 December 2006 17:33, David Abrahams wrote:
> 
> I keep seeing BBv1 dependencies in our supposedly-v2
scripts,
> Jamfiles, and documentation.  For example
$BOOST_ROOT/Jamfile.v2 uses
> the --with-python-root option to set the PYTHON_ROOT
variable, which
> has no effect in v2.  

This specific issue is:

	h
ttps://zigzag.cs.msu.su:7813/boost.build/ticket/61

I'm don't know what's right solution to it, do you?
	
> $BOOST_ROOT/configure isn't designed to work 
> with BBv2 it seems.

I think it works now.

> http://www.boost-consulting.com/boost/more/s
eparate_compilation.html
> still needs to be updated for BBv2.  

Is there a ticket for it?

> I'm concerned that many more 
> instances of this problem may exist, and I'm not sure
how to resolve
> them.  Is there a reasonable automated search we could
use?

I don't know, maybe "grep bjam".

- Volodya

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

Vladimir Prus <ghostcs.msu.su> writes:

> On Sunday 10 December 2006 17:33, David Abrahams wrote:
>> 
>> I keep seeing BBv1 dependencies in our
supposedly-v2 scripts,
>> Jamfiles, and documentation.  For example
$BOOST_ROOT/Jamfile.v2 uses
>> the --with-python-root option to set the
PYTHON_ROOT variable, which
>> has no effect in v2.  
>
> This specific issue is:
>
> 	h
ttps://zigzag.cs.msu.su:7813/boost.build/ticket/61
>
> I'm don't know what's right solution to it, do you?

Get the person who wrote the Jamfile to remove the v1
idioms?

>> $BOOST_ROOT/configure isn't designed to work with
BBv2 it seems.
>
> I think it works now.

Maybe.  It's still doing all this Python version detection
that is
already done by python.jam

>> http://www.boost-consulting.com/boost/more/s
eparate_compilation.html
>> still needs to be updated for BBv2.  
>
> Is there a ticket for it?

I don't know.  Is it a BB issue?

>> I'm concerned that many more instances of this
problem may exist,
>> and I'm not sure how to resolve them.  Is there a
reasonable
>> automated search we could use?
>
> I don't know, maybe "grep bjam".

I s'pose.  Who is going to inspect the results?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Saturday 06 January 2007 17:58, David Abrahams wrote:
> Vladimir Prus <ghostcs.msu.su> writes:
> 
> > On Sunday 10 December 2006 17:33, David Abrahams
wrote:
> >> 
> >> I keep seeing BBv1 dependencies in our
supposedly-v2 scripts,
> >> Jamfiles, and documentation.  For example
$BOOST_ROOT/Jamfile.v2 uses
> >> the --with-python-root option to set the
PYTHON_ROOT variable, which
> >> has no effect in v2.  
> >
> > This specific issue is:
> >
> > 	h
ttps://zigzag.cs.msu.su:7813/boost.build/ticket/61
> >
> > I'm don't know what's right solution to it, do
you?
> 
> Get the person who wrote the Jamfile to remove the v1
idioms?

That's rather imprecise. If you want *me* to fix that, you'd
need to tell me exactly
that the --with-python-root should do. Especially when
python is already initalized in
user-config.jam.

> >> $BOOST_ROOT/configure isn't designed to work
with BBv2 it seems.
> >
> > I think it works now.
> 
> Maybe.  It's still doing all this Python version
detection that is
> already done by python.jam

That's a question to Doug. If he or you have the time to
remove that,
great. Otherwise, we'd have to release what we have.

> 
> >> http://www.boost-consulting.com/boost/more/s
eparate_compilation.html
> >> still needs to be updated for BBv2.  
> >
> > Is there a ticket for it?
> 
> I don't know.  Is it a BB issue?
> 
> >> I'm concerned that many more instances of this
problem may exist,
> >> and I'm not sure how to resolve them.  Is
there a reasonable
> >> automated search we could use?
> >
> > I don't know, maybe "grep bjam".
> 
> I s'pose.  Who is going to inspect the results?

That's again a bit indirect wording. I've just did, the
result is attached.
I'm gonna provide more thought on this in reply to Thomas.

- Volodya



libs/date_time/xmldoc/buildinfo.xml

    Requires update to V2.

libs/iostreams/doc/installation.html

    Needs update.    

libs/python/doc/building.html

    Needs update.

libs/python/doc/tutorial/doc/html/python/hello.html
libs/python/doc/tutorial/doc/tutorial.qbk
libs/python/doc/v2/faq.html
libs/python/example/README

    Did not look.
    
libs/regex/doc/install.html

    Needs update.

libs/serialization/doc/archive_reference.html

    Needs update.
    
libs/serialization/test/runtest.bat
libs/serialization/test/runtest.ksh
libs/serialization/test/runtest.sh

    Need update.

libs/signals/doc/tutorial.xml

    Possibly needs update.

libs/statechart/test/RunTests.bat

    Needs update.

libs/statechart/example/BuildExamples.bat

    Needs update.

libs/test/doc/components/prg_exec_monitor/compilation.html

    Needs update.

libs/test/doc/components/utf/compilation.html

    Needs update.

libs/test/test/auto-link-test/run_bjam.bat

    Needs update.

libs/thread/doc/build.xml

    Needs update.

more/separate_compilation.html
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Jan 6, 2007, at 4:03 PM, Vladimir Prus wrote:

> On Saturday 06 January 2007 17:58, David Abrahams
wrote:
>> Vladimir Prus <ghostcs.msu.su> writes:
>>
>>> On Sunday 10 December 2006 17:33, David
Abrahams wrote:
>>>> $BOOST_ROOT/configure isn't designed to
work with BBv2 it seems.
>>>
>>> I think it works now.
>>
>> Maybe.  It's still doing all this Python version
detection that is
>> already done by python.jam
>
> That's a question to Doug. If he or you have the time
to remove that,
> great. Otherwise, we'd have to release what we have.

I thought I answered this already? Anyway...

"configure" needs to look for Python because it
needs to know whether  
it should add a "using python" line to its own
user-config.jam file.  
And once it has found Python, the best way to be sure that
it then  
builds with the Python it found is by putting the detected
root and  
version into its user-config.jam.

If we let BBv2 find Python at "make" time, it
could find a different  
Python from what "configure" found (due to changes
to the PATH, for  
example).

	Cheers,
	Doug
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Wasn't it mapperzgooglemail.com who wrote:
>
>Mike Williams is the guy who uaually reports on this.
>Guess he is busy. There are others that can report on
it.

I'm not going to be putting MSIE7 on my computer for a
while.

The problem doesn't occur in MSIE6.

-- 
The Blackpool Community Church Javascript Team 
http://www.
econym.demon.co.uk/googlemaps/

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the
Google Groups "Google Maps API" group.
To post to this group, send email to Google-Maps-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Maps-API-unsubscribegooglegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Wasn't it Don Russell who wrote:
>
>maps.huge.info wrote:
>> I read on Apple's site that the phone did have GPS.
It would be cool if
>> that GPS device could be tied into the map.
>>
>> -John Coryat
>
>Wouldn't that violate the googlemaps TOS? When I
registered for a google 
>maps key, one of the items in the TOS was that I would
not make 
>something that would track position in (near) real
time.
>
>i.e. If I have a gps gizmo in my car and attach it to my
laptop in my 
>car, I can't (by the TOS) develop a map that shows me
where I am and 
>track my position.
>
>I think that would be very cool though...

You can use such a GPS system for tracking where a vehicle
or phone has
been, but you can't use it for real-time route guidance.

At the bottom of section 1.4 of the API terms:

  In addition, the Service may not be used: (a) for or with
real time 
  route guidance (including without limitation, turn-by-turn
route 
  guidance and other routing that is enabled through the use
of a 
  sensor), or (b) for, or in connection with, any systems or
functions 
  for automatic or autonomous control of vehicle behavior.

My guess is that it's a safety/litigation issue. If you
crash your car
because you needed both hands to operate such a guidance
system, then
you can't sue Google, because they told you not to do it.
(It might also
be that the companies that licence the map data to Google
are also
involved in the manufacture of SatNav devices, and would
prefer you to
buy a real SatNav.)

-- 
The Blackpool Community Church Javascript Team 
http://www.
econym.demon.co.uk/googlemaps/

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the
Google Groups "Google Maps API" group.
To post to this group, send email to Google-Maps-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Maps-API-unsubscribegooglegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---