Bradley Lucier wrote:
It should be
configure make bootstrap hg pull make update <<<<<<<<<<<<<<<<<< not hg update
I'm trying it now.
Thank you Bradley, it worked out!
I think the process is a little confusing because after doing the hg pull, hg is telling us to do "hg update" which seemed to broke my gambit sources hehe. Could it be possible for make update to include the hg pull statement, which would simplify the update process and avoid confusion?
Thanks again!
David
Afficher les réponses par date
On 17-Mar-08, at 11:30 AM, Bradley Lucier wrote:
On Mar 17, 2008, at 11:27 AM, David St-Hilaire wrote:
Could it be possible for make update to include the hg pull statement, which would simplify the update process and avoid confusion?
I think that's a good idea.
Done.
Now it is sufficient to do "make update" to bring your working copy of Gambit in sync with the latest sources on the Gambit source code repository.
Marc
On Mar 17, 2008, at 12:12 PM, Marc Feeley wrote:
On 17-Mar-08, at 11:30 AM, Bradley Lucier wrote:
On Mar 17, 2008, at 11:27 AM, David St-Hilaire wrote:
Could it be possible for make update to include the hg pull statement, which would simplify the update process and avoid confusion?
I think that's a good idea.
Done.
Now it is sufficient to do "make update" to bring your working copy of Gambit in sync with the latest sources on the Gambit source code repository.
Marc:
Does the new sequence of operations for "make update" end with a "make" or an "hg pull"? It would probably be best if it ended with a "make".
Brad
On 17-Mar-08, at 12:44 PM, Bradley Lucier wrote:
Marc:
Does the new sequence of operations for "make update" end with a "make" or an "hg pull"? It would probably be best if it ended with a "make".
It now ends in a make. I will add another target "update-nomake" that doesn't do an "hg pull" or a final "make" because in some cases you want more control over the pull and final make.
Marc
-
Bradley Lucier -
David St-Hilaire -
Marc Feeley