<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
How do I go about contributing these edits once I get it all<br>
working?<br>
</blockquote>
<br></div>
Best way, is to fork the pgrouting respository, make your changes there and issue a pull request so we can merge your changes.<br></blockquote><div><br></div><div style>For sure this would be easiest and best solution.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
If there are not too many changes, you could do something like:<br>
<br>
git diff > mychanges-diff.txt<br>
<br>
And open a ticket and attache the diff file to the ticket.<br></blockquote><div><br></div><div style>I think Github doesn't allow to attach files to tickets (just looked for it last week), but an alternative would be to use Gist: <a href="https://gist.github.com/">https://gist.github.com/</a></div>
<div style><br></div><div style>Nevertheless, to fork the repository and then submit a pull request would be better:</div><div style><a href="https://help.github.com/articles/using-pull-requests">https://help.github.com/articles/using-pull-requests</a><br>
</div><div style><br></div><div style>Daniel</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
-Steve<div class=""><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Best, Alec<br>
<br>
<br>
<br>
<br>
On May 8, 2013, at 11:55 AM, Stephen Woodbridge<br>
<<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi sanak,<br>
<br>
I looked at your changes below, and they do not seem to be based on<br>
my branch "sew-devel-2_0". The quick tell is that my source starts<br>
at "src/" and not "core/" as your changes reflect.<br>
<br>
For linux I compile, install and test using:<br>
<br>
tools/doit (cd build; sudo make install) tools/<a href="http://testrunner.pl" target="_blank">testrunner.pl</a><br>
<br>
In the C/C++ code you should be able to use:<br>
<br>
#ifdef __APPLE__ ... #else ... #endif<br>
<br>
and in cmake you can use:<br>
<br>
if(APPLE) ... else(APPLE) ... endif(APPLE)<br>
<br>
Can you also post what the results of:<br>
<br>
echo | g++ -dM -E -<br>
<br>
when run on OSX.<br>
<br>
No hurray, when you can get to it, this weekend is fine.<br>
<br>
Thanks, -Steve<br>
<br>
On 5/7/2013 6:05 PM, sanak wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi Alec, Stephen,<br>
<br>
About 1 month ago, I tried Mac ports build in my private<br>
branch("macports") which is based on "sew-revel-2_0", and<br>
confirmed that it can build with Mac OSX 10.8(Mountain Lion).<br>
<a href="https://github.com/sanak/pgrouting4w/commit/7291a7b6be3bd37c9e507048bfe3ba0fcf0c5c6e" target="_blank">https://github.com/sanak/<u></u>pgrouting4w/commit/<u></u>7291a7b6be3bd37c9e507048bfe3ba<u></u>0fcf0c5c6e</a><br>
<br>
<br>
<br>
</blockquote></blockquote></blockquote>
Now, I am busy for other task, but, I will check and test it in this<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
weekend.<br>
<br>
<br>
<br>
2013/5/8 Stephen Woodbridge <<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.com</a><br>
<mailto:<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.<u></u>com</a>>><br>
<br>
On 5/7/2013 10:27 AM, Alec Gosse wrote:<br>
<br>
Hello all,<br>
<br>
I am working on a bicycle routing project and converting from<br>
Open Trip Planner to pgRouting on both OSX and 64bit Ubuntu with<br>
PostgreSQL 9.1+. For me, the sew-revel-2_0 branch will build<br>
under ubuntu 12.10, but not on OSX 10.8 using dependencies<br>
installed through Homebrew.<br>
<br>
Homebrew is certainly the best way I've found to install<br>
open-source tools on a mac, so I would like to help get pgRouting<br>
2.0 installable that way. Homebrew tends to use quite current<br>
packages such as boost 1.53, however, but I see in tool/NOTES.txt<br>
that pgRouting requires boost 1.46.1? Since things build on<br>
Ubuntu using boost 1.49, I'm wondering if this still applies?<br>
<br>
<br>
Well the required version is whatever you can get to work. I<br>
know there are some problems with 1.47, but those might be<br>
specific to that version.<br>
<br>
<br>
In either case, what's the best way for me to help get things<br>
running under OSX? Should I post errors I can't resolve to the<br>
list, and or is someone already working on this?<br>
<br>
<br>
Yes, We can try to help if we know what errors you are seeing.<br>
I'm not sure anyone here has OSX so you might need to take some<br>
initiative to figure things out. If you look at the<br>
CMakeLists.txt files that are sprinkled throughout the project<br>
tree, you will see that some of them have blocks like:<br>
<br>
if(APPLE) ... endif(APPLE)<br>
<br>
maybe we don't have these setup correctly or maybe some are<br>
missing that need to be added. It would be great if you can help<br>
with this.<br>
<br>
Thanks, -Steve<br>
<br>
<br>
Best, Conrad (Alec) Gosse, MUEP Doctoral Candidate: Civil &<br>
Environmental Engineering University of Virginia Charlottesville,<br>
VA<br>
<br>
On May 7, 2013, at 1:40 AM, Daniel Kastl <<a href="mailto:daniel@georepublic.de" target="_blank">daniel@georepublic.de</a><br>
<mailto:<a href="mailto:daniel@georepublic.de" target="_blank">daniel@georepublic.de</a>><u></u>> wrote:<br>
<br>
Hi Razequl,<br>
<br>
The currently used branch is named "sew-devel-2_0" (we're<br>
planning to rename it to "develop" some time). You find all the<br>
necessary steps to compile explained on the Github readme:<br>
<a href="https://github.com/pgrouting/__pgrouting/tree/sew-devel-2_0" target="_blank">https://github.com/pgrouting/_<u></u>_pgrouting/tree/sew-devel-2_0</a><br>
<<a href="https://github.com/pgrouting/pgrouting/tree/sew-devel-2_0" target="_blank">https://github.com/pgrouting/<u></u>pgrouting/tree/sew-devel-2_0</a>><br>
<br>
If you want to compile with support for "Driving Distance", then<br>
you need to have CGAL libraries as dependency. GAUL dependency<br>
is gone.<br>
<br>
Daniel<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Tue, May 7, 2013 at 2:35 PM, Razequl Islam<br>
<<a href="mailto:ziboncsedu@gmail.com" target="_blank">ziboncsedu@gmail.com</a> <mailto:<a href="mailto:ziboncsedu@gmail.com" target="_blank">ziboncsedu@gmail.com</a>>> wrote: Hi<br>
Steve, I also want to have a look at the possible problem. I am<br>
trying to set up the environment on my machine. I have the<br>
previous version. What do I need to do to get 2.0 working? Should<br>
I set up the environment from the scratch or should an update<br>
will do. Please let me know how I should proceed. I can also do<br>
the debugging once I have the environment in place.<br>
<br>
Thanks. - Razequl<br>
<br>
<br>
<br>
On Mon, May 6, 2013 at 11:32 PM, Stephen Woodbridge<br>
<<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.com</a> <mailto:<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.<u></u>com</a>>> wrote:<br>
Hi Razequl,<br>
<br>
I have been trying to integrate your bidirectional shortest path<br>
code. I have merged the code into my pgrouting branch<br>
"sew-devel-2_0", but it is crashing the back-end with a segv.<br>
<br>
If you have time and want to look into this that would be great<br>
as I would like to get this code working in 2.0.<br>
<br>
I'm not sure if I found a bug in your code or I broke something<br>
when I merged it, or for that matter that I even merged the<br>
correct code :) because you sent email indicating that you fixed<br>
stuff. I merged the code from master at<br>
<a href="https://github.com/zibon/__pgrouting" target="_blank">https://github.com/zibon/__<u></u>pgrouting</a><br>
<<a href="https://github.com/zibon/pgrouting" target="_blank">https://github.com/zibon/<u></u>pgrouting</a>><br>
<br>
I also ran into an issue that when I merged you code into the<br>
code library, that the trsp broke, then take you code out and it<br>
works again. I assume that there is some kind of function name<br>
or global initialization issue. This does not seem to be an issue<br>
for trsp now that the bi-dir code is in a separate library.<br>
<br>
This might give you a chance to get your development/test/debug<br>
environment setup and to familiarize yourself with the new<br>
source code layout.<br>
<br>
Let me know if you have time and I'll help point the way. If you<br>
are tied up with class work, etc that clearly takes priority.<br>
<br>
Thanks, -Steve<br>
<br>
<br>
______________________________<u></u>___________________ pgrouting-dev<br>
mailing list <a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<mailto:<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/__mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/__<u></u>mailman/listinfo/pgrouting-dev</a><br>
<<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><u></u>><br>
<br>
<br>
<br>
<br>
-- Georepublic UG & Georepublic Japan eMail:<br>
<a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@georepublic.de</a> <mailto:<a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@<u></u>georepublic.de</a>><br>
Web: <a href="http://georepublic.de" target="_blank">http://georepublic.de</a><br>
______________________________<u></u>___________________ pgrouting-dev<br>
mailing list <a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<mailto:<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/__mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/__<u></u>mailman/listinfo/pgrouting-dev</a><br>
<<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><u></u>><br>
<br>
<br>
______________________________<u></u>___________________ pgrouting-dev<br>
mailing list <a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<mailto:<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/__mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/__<u></u>mailman/listinfo/pgrouting-dev</a><br>
<<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><u></u>><br>
<br>
<br>
______________________________<u></u>___________________ pgrouting-dev<br>
mailing list <a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<mailto:<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/__mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/__<u></u>mailman/listinfo/pgrouting-dev</a><br>
<<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><u></u>><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________ pgrouting-dev<br>
mailing list <a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________ pgrouting-dev<br>
mailing list <a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
</blockquote>
<br>
______________________________<u></u>_________________ pgrouting-dev mailing<br>
list <a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse">Georepublic UG & Georepublic Japan<br>eMail: <a href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66,99,171)" target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a href="http://georepublic.de/" style="color:rgb(66,99,171)" target="_blank">http://georepublic.de</a></span>
</div></div>