[mapguide-users] Spatial

[Jackie Ng]

Hi Pierre,

Geometry, and most of the projects in the MapGuide codebase in general are
configured as unity builds.

In this configuration, there is a single .cpp file that #includes all other
.cpp files in the project. This is/was done to reduce build/compile times
by maximizing disk I/O throughput because there is only one translation
unit to process (the unity .cpp file).

You can see the .cpp files in question being #include'd in a unity
GeometryBuild.cpp file for the Geometry project:

https://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/Geometry/GeometryBuild.cpp#L117

Most projects across the common, server and web tier solutions follow the
same convention. If you open any of these solutions and take a look at the
projects, you will see all .cpp files except for the $PROJECTBuild.cpp file
marked as being excluded from compilation.

- Jackie

You wrote:

Hi,



During the process of checking the defect #2257
https://trac.osgeo.org/mapguide/ticket/2257  , I have noticed that the
files MathUtility.cpp, SpatialUtility.cpp and SpatialUtilityCircularArc.cpp
for Spatial are never compiled in the project Geometry (Server solution).
Is it normal ?



Regards,



Pierre C.



-- 
*Please Note: I no longer create new posts or post replies to any OSGeo
mailing list through nabble. As a result, you most likely won't see this
message appear on nabble's view of any OSGeo mailing list and may only see
this message through mailing list archives or depending on your mailing
list subscription settings, through daily message digests or automated
notifications from the mailing lists.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20220614/bce8df17/attachment.htm>