EditableProject Template for External Plugins about meshlib HOT 5 CLOSED

Thanks @Grantim. This is not a pressing matter. Having followed your steps, I was able to remove the dependency on OpenVDB and now my plugin again works well with Rhino.

Thanks for a super fast response as usual!

As far as I am concerned, this issue can be closed now.

from meshlib.

Hello!

I suggest in your case the easiest way is to have MeshLib as submodule of your solution like this

and with CustomMRProps.props you can define any of these macro

option(MRMESH_NO_CLIPBOARD "Disable clipboard support for Linux and Mac" OFF)
option(MRMESH_NO_PDF "Disable PDF support" OFF)
option(MRMESH_NO_CPR "Disable CPR tests" OFF)
option(MRMESH_NO_PYTHON "Disable Python bindings" OFF)
option(MRMESH_NO_DICOM "Disable DICOM image support" OFF)
option(MRMESH_NO_LABEL "Disable support of label objects" OFF)
option(MRMESH_NO_JPEG "Disable JPEG support" OFF)
option(MRMESH_NO_PNG "Disable PNG support" OFF)
option(MRMESH_NO_TIFF "Disable TIFF support" OFF)
option(MRMESH_NO_VOXEL "Disable voxel support" OFF) # openvdb
option(MRMESH_NO_GLTF "Disable glTF support" OFF)
option(MRMESH_NO_XML "Disable XML support (affects 3MF support)" OFF)
option(MRMESH_NO_E57 "Disable E57 support" OFF)
option(MRMESH_NO_OPENCASCADE "Disable OpenCASCADE usage" OFF)
option(MRMESH_NO_ZLIB "Disable Zlib usage" OFF)

So you will be able to reduce number of dependencies (we didn't really test it on windows, but I believe it should work)

So your solution should look like this

CustomMRProps.props file:

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <_ProjectFileVersion>10.0.40219.1</_ProjectFileVersion>
    <_PropertySheetDisplayName>Common properties customizatoin</_PropertySheetDisplayName>
  </PropertyGroup>
  <ItemDefinitionGroup>
    <ClCompile>
      <PreprocessorDefinitions>MRMESH_NO_PNG;MRMESH_NO_JPEG;MRMESH_NO_DICOM;MRMESH_NO_PDF;MRMESH_NO_XML;MRMESH_NO_GLTF;MRMESH_NO_ZLIB;MRMESH_NO_CLIPBOARD;MRMESH_NO_E57;MRMESH_NO_CPR;MRMESH_NO_VOXEL;MRMESH_NO_OPENCASCADE;_ITERATOR_DEBUG_LEVEL=0;%(PreprocessorDefinitions)</PreprocessorDefinitions>
    </ClCompile>
  </ItemDefinitionGroup>
</Project>

MeshLibWrapper.vcxproj file:

     </ImportGroup>
+++  <Import Project="$(ProjectDir)\..\..\MeshLib\source\common.props" />
     <PropertyGroup Label="UserMacros" />

SubmoduleSolution.zip

from meshlib.

Looks super good! Will test and report back. Thanks @Grantim!

from meshlib.

Thanks @Grantim, this looks very promising. I took your example and build it with the following settings:

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <_ProjectFileVersion>10.0.40219.1</_ProjectFileVersion>
    <_PropertySheetDisplayName>Common properties customizatoin</_PropertySheetDisplayName>
  </PropertyGroup>
  <ItemDefinitionGroup>
    <ClCompile>
      <PreprocessorDefinitions>
	  MRMESH_NO_CLIPBOARD;
	  MRMESH_NO_PDF;
	  MRMESH_NO_CPR;
	  MRMESH_NO_PYTHON;
	  MRMESH_NO_DICOM;
	  MRMESH_NO_LABEL;
	  MRMESH_NO_JPEG;
	  MRMESH_NO_PNG;
	  MRMESH_NO_TIFF;
	  MRMESH_NO_VOXEL;
	  MRMESH_NO_GLTF;
	  MRMESH_NO_XML;
	  MRMESH_NO_E57;
	  MRMESH_NO_OPENCASCADE;
	  MRMESH_NO_ZLIB;
	  _ITERATOR_DEBUG_LEVEL=0;%(PreprocessorDefinitions)
	  </PreprocessorDefinitions>
    </ClCompile>
  </ItemDefinitionGroup>
</Project>

But still see Python in the output even though it's explicitly excluded above:

from meshlib.

But still see Python in the output even though it's explicitly excluded above:

Python is copied as post build script for MRMesh, its hard to skip this now, anyway I think it is not linked to main dll, so you can remove them from final distribution

EDIT: Probably it is linked, unfortunately to get rid of python in this case it will require some changes in MeshLib (zip file is not used)

from meshlib.