Joe Kaplan

I'm working on a package in MIN. I'd like to be able to build for both Mac and Windows. I would like to store my work in a github repo and be able to push and pull from either platform to that things stay in sync.

I recognized that in the Source folder of the min package there is "min-api" and "min-lib" and these files are different depending on the platform.

So I can't just but the whole package under source control and expect it work under both platforms. I can put those two folder in .gitignore. And I've been able to upload a repo that I think has all the platform agnotstic data I want to source control.

But I'm still having a hard time setting up a new dev environment. I can create a fresh Min Package. They download my repo, overwrite the files I need to, and everything builds. But getting my new local build to push and pull to my github repo is causing me trouble. Since I did not clone the repo, Xcode gets pretty confused and is giving me errors when I try to push my new build setup back to GitHub.

This may be more of a Git/Github question, but I was wondering if anybody else has devised a means of cross-platform Min development syncing to single GitHub repo. Maybe there's an easy solution that I've just missed.

I'm working on a package in MIN.  I'd like to be able to build for both Mac and Windows.  I would like to store my work in a github repo and be able to push and pull from either platform to that things stay in sync.

So I can't just but the whole package under source control and expect it work under both platforms.  I can put those two folder in .gitignore. And I've been able to upload a repo that I think has all the platform agnotstic data I want to source control.

But I'm still having a hard time setting up a new dev environment.  I can create a fresh Min Package.  They download my repo, overwrite the files I need to, and everything builds.  But getting my new local build to push and pull to my github repo is causing me trouble.  Since I did not clone the repo, Xcode gets pretty confused and is giving me errors when I try to push my new build setup back to GitHub.

This may be more of a Git/Github question, but I was wondering if anybody else has devised a means of cross-platform Min development syncing to single GitHub repo.  Maybe there's an easy solution that I've just missed.

Greetings,
I'm working on a package in MIN.  I'd like to be able to build for both Mac and Windows.  I would like to store my work in a gith

min-development-best-practice-crossplatform-github-repo

min-api and min-lib should be exactly the same across platforms, so not sure what you are referring to. both can be added to a cross-platform repo with no issues, although the recommended practice is adding as sub-modules. any of the c74 public repos that are based on min (e.g. jit.mo) are cross-platform projects, so maybe check that setup.

I figured this out shortly after posting. The min-lib and min-api folders are platform agnostic before running "Cmake -G Xcode .." to build the project files. But it appears that the cmake scripts do operate on those folders in platform specific ways. I know this because I tried running cmake on my Windows machine, then moving those files to my Mac and trying to build my externals. I got a handful of undefined symbol errors.

Once I discovered that I needed to include the pre-cmake version of "min-lib" and "min-api" in my repository I ended up doing exactly what you suggested: I added the folders as submodules directly from the c74 repos.

I did need to add those folders to .gitignore in the package root though, to prevent platform agnostic files from being replaced with platform specific files in the repo after generating the projects.

I figured this out shortly after posting.  The min-lib and min-api folders are platform agnostic before running "Cmake -G Xcode .." to build the project files.  But it appears that the cmake scripts do operate on those folders in platform specific ways.    I know this because I tried running cmake on my Windows machine, then moving those files to my Mac and trying to build my externals.  I got a handful of undefined symbol errors.

Once  I discovered that I needed to include the pre-cmake version of "min-lib" and "min-api" in my repository I ended up doing exactly what you suggested:  I added the folders as submodules directly from the c74 repos.

I did need to add those folders to .gitignore in the package root though, to prevent platform agnostic files from being replaced with platform specific files in the repo after generating the projects. 

nothing should be added to those locations when running cmake. all cmake build artifacts should be placed in the build folder (that you are running cmake from), so maybe you're missing a step somewhere when running cmake, e.g. mkdir build and cd build from the root repo prior to running cmake? the build directory should be added to the .gitignore, 

nothing should be added to those locations when running cmake. all cmake build artifacts should be placed in the build folder (that you are running cmake from), so maybe you're missing a step somewhere when running cmake, e.g. mkdir build and cd build from the root repo prior to running cmake? the build directory should be added to the .gitignore, which it is by default in min-devkit.

My package has a bunch of .vcxproj files, etc., in ../source/min-lib. When I moved my whole package folder (except for ../build) over to my Mac, it was unhappy.

I thought I tested this on a fresh package. But when I'm trying it now, it is definitely behaving the way you're saying it should. I just replaced ../source/min-lib and ../source/min-api in my working package with fresh copies of those folders from the vanilla package and everything seems well. So Rob must be right, of course. :)

My package folder went through a lot in the early stages when I was experimenting and figuring stuff out, so I'm not surprised it got deformed somehow. I guess something must've been wrong with my testing yesterday when I was trying to see if this was unique to my package.

I'll leave the submodules in, but take those folders out of .gitignore. Thanks!

My package has a bunch of  .vcxproj files, etc., in ../source/min-lib.  When I moved my whole package folder (except for ../build) over to my Mac, it was unhappy.

I thought I tested this on a fresh package.  But when I'm trying it now, it is definitely behaving the way you're saying it should.  I just replaced ../source/min-lib and ../source/min-api in my working package with fresh copies of those folders from the vanilla package and everything seems well.  So Rob must be right, of course. :)

My package folder went through a lot in the early stages when I was experimenting and figuring stuff out, so I'm not surprised it got deformed somehow.   I guess something must've been wrong with my testing yesterday when I was trying to see if this was unique to my package.

I'll leave the submodules in, but take those folders out of .gitignore.  Thanks!

MIN Development Best Practice: CrossPlatform Github repo?