I've opened tickets #2371 and #2372

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

I've opened tickets #2371 and #2372

Gabriele Monfardini
Hi all,

I've opened tickets http://trac.osgeo.org/mapguide/ticket/2371 and
http://trac.osgeo.org/mapguide/ticket/2372

I would like to receive some feedback from current developers.

If some steps are done in the hoped direction (e.g. decoupling mapguide
configuration from vanilla codebase) I would like to help in easing
building process under Linux.

Regards,

Gabriele Monfardini
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Reply | Threaded
Open this post in threaded view
|

Re: I've opened tickets #2371 and #2372

zspitzer
this is a massive pain point for mapguide, the solution on linux is to
use the system modules which are kept up to date, but this does involve
a lot of work

this needs to be written up as a RFC


On Tue, Oct 22, 2013 at 7:59 PM, Gabriele Monfardini
<[hidden email]>wrote:

> Hi all,
>
> I've opened tickets http://trac.osgeo.org/mapguide/ticket/2371 and
> http://trac.osgeo.org/mapguide/ticket/2372
>
> I would like to receive some feedback from current developers.
>
> If some steps are done in the hoped direction (e.g. decoupling mapguide
> configuration from vanilla codebase) I would like to help in easing
> building process under Linux.
>
> Regards,
>
> Gabriele Monfardini
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



--
Zac Spitzer
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Reply | Threaded
Open this post in threaded view
|

Re: I've opened tickets #2371 and #2372

Gabriele Monfardini
Hi Zac,

this is a massive pain point for mapguide, the solution on linux is to
> use the system modules which are kept up to date, but this does involve
> a lot of work
>

the same is for Windows, only installation of uptodate software is
different.
But use buggy and old versions is difficult to accept also on Windows.

Probably the first step could be do some preparatory work during next round
of update, starting decoupling mapguide specific part (as afaik has been
done for openlayers).

this needs to be written up as a RFC


Agree.
I've opened the bug to see if this question is considered important by the
developer or just an annoyance (or maybe important but too much work with
current number of developers).

Regards,

Gabriele Monfardini
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Reply | Threaded
Open this post in threaded view
|

Re: I've opened tickets #2371 and #2372

Jackie Ng
We've already somewhat decoupled MapGuide from our oem-specific Apache/PHP in 2.6 as part of the Apache/PHP/Tomcat component upgrade. Apache/PHP include and linker paths are now parameterized via environment variables and we do keep track of any custom modifications. Although not truly tested, it means we should now be able to build MapGuide against an alternate installation of Apache/PHP.

This would have to be done through multiple phases.

 1. Parameterize our linker/include paths for all oem libraries used by MapGuide via environment variables. As already explained, we've done this for Apache/PHP in 2.6.

 2. Doing this, we can then move the Oem tree up one level in the svn repo to be a sibling of MgDev and not a child directory and set default linker/include paths to be based on this assumption. This means the default preferred check out goes from this:

 [svn wc] MgDev
     - Oem
     - Common
     - Server
     - Web
     - ...

To this

 [svn wc] Oem
 [svn wc] MgDev
     - Server
     - Common
     - Web
     - ...

This way you have the option of doing a light checkout of MgDev and fixing up the environment variables to point to the desired versions of the libraries you want to build MapGuide against if you do not wish to do a svn checkout of Oem.

Will have to think this out a bit more, but this is something definitely worth improving.

- Jackie
Reply | Threaded
Open this post in threaded view
|

Re: I've opened tickets #2371 and #2372

Gabriele Monfardini
Thank you for the reply Jackie and for the good news.
I'll wait for 2.6 to make some test.

Regards,

Gabriele
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals