Workflow issue with Cmake and Max patch editing

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

Workflow issue with Cmake and Max patch editing

Trond Lossius
Administrator
Hi,

With the recent final move from ruby-script building to Cmake, I realise that we now have one minor workflow inconvenience with respect to development of Max patchers and similar non-C++ files in the JamomaMax repository. All files now gets copied to build/Jamoma/JamomaInstall/jamoma, and from Max7 we’ll set up a symbolic link / alas from the packages folder to this folder.

This implies that if I want to do modification to max patchers, I either have to open them from Finder not e.g. from the File Browser in Max, but instead from the repository, and once saved, I’ll have to rebuild in order to have the new file becoming available to Max.

Is there a way that we can change this so that developers can link to the versioned JamomaMax/Jamoma folder and be able to do development on the files of this folder, with immediate availability in Max?

Thanks,
Trond
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
tap
Reply | Threaded
Open this post in threaded view
|

Re: Workflow issue with Cmake and Max patch editing

tap
Hi Trond,

On my machine what I see is that the builds are also copied from e.g. 
  build/Jamoma/JamomaInstall/jamoma/JamomaMax/Jamoma/externals
to
  Jamoma/externals

So just making an alias to "Jamoma" works fine here.  Does this work for you?


Tim


On Thu, Sep 3, 2015 at 8:31 AM, Trond Lossius <[hidden email]> wrote:
Hi,

With the recent final move from ruby-script building to Cmake, I realise that we now have one minor workflow inconvenience with respect to development of Max patchers and similar non-C++ files in the JamomaMax repository. All files now gets copied to build/Jamoma/JamomaInstall/jamoma, and from Max7 we’ll set up a symbolic link / alas from the packages folder to this folder.

This implies that if I want to do modification to max patchers, I either have to open them from Finder not e.g. from the File Browser in Max, but instead from the repository, and once saved, I’ll have to rebuild in order to have the new file becoming available to Max.

Is there a way that we can change this so that developers can link to the versioned JamomaMax/Jamoma folder and be able to do development on the files of this folder, with immediate availability in Max?

Thanks,
Trond
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel


------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
jln
Reply | Threaded
Open this post in threaded view
|

Re: Workflow issue with Cmake and Max patch editing

jln
Administrator
Mathieu told me yesterday that he noticed the cmake worked the way you mention Tim, one time out of two or something like this. Am I correct Mathieu ?

Best,
Julien




On Thu, Sep 3, 2015 at 4:39 PM, Timothy Place <[hidden email]> wrote:

Hi Trond,

On my machine what I see is that the builds are also copied from e.g. 
  build/Jamoma/JamomaInstall/jamoma/JamomaMax/Jamoma/externals
to
  Jamoma/externals

So just making an alias to "Jamoma" works fine here.  Does this work for you?


Tim


On Thu, Sep 3, 2015 at 8:31 AM, Trond Lossius <[hidden email]> wrote:
Hi,

With the recent final move from ruby-script building to Cmake, I realise that we now have one minor workflow inconvenience with respect to development of Max patchers and similar non-C++ files in the JamomaMax repository. All files now gets copied to build/Jamoma/JamomaInstall/jamoma, and from Max7 we’ll set up a symbolic link / alas from the packages folder to this folder.

This implies that if I want to do modification to max patchers, I either have to open them from Finder not e.g. from the File Browser in Max, but instead from the repository, and once saved, I’ll have to rebuild in order to have the new file becoming available to Max.

Is there a way that we can change this so that developers can link to the versioned JamomaMax/Jamoma folder and be able to do development on the files of this folder, with immediate availability in Max?

Thanks,
Trond
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel



------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
Reply | Threaded
Open this post in threaded view
|

Re: Workflow issue with Cmake and Max patch editing

Mathieu CHAMAGNE
well... *sometime* it fails copying externals, complaining that the folder is not empty... :-s
but most of the time, it works !!
and if you just alias the Jamoma folder to Max7 packages, it seems to be ok.
I can modify patchers, and commit them to git ; so I don't see any problem here...

m

________________
Mathieu Chamagne
[hidden email]
http://mathieuchamagne.com

2015-09-03 16:43 GMT+02:00 Julien Rabin <[hidden email]>:
Mathieu told me yesterday that he noticed the cmake worked the way you mention Tim, one time out of two or something like this. Am I correct Mathieu ?

Best,
Julien




On Thu, Sep 3, 2015 at 4:39 PM, Timothy Place <[hidden email]> wrote:

Hi Trond,

On my machine what I see is that the builds are also copied from e.g. 
  build/Jamoma/JamomaInstall/jamoma/JamomaMax/Jamoma/externals
to
  Jamoma/externals

So just making an alias to "Jamoma" works fine here.  Does this work for you?


Tim


On Thu, Sep 3, 2015 at 8:31 AM, Trond Lossius <[hidden email]> wrote:
Hi,

With the recent final move from ruby-script building to Cmake, I realise that we now have one minor workflow inconvenience with respect to development of Max patchers and similar non-C++ files in the JamomaMax repository. All files now gets copied to build/Jamoma/JamomaInstall/jamoma, and from Max7 we’ll set up a symbolic link / alas from the packages folder to this folder.

This implies that if I want to do modification to max patchers, I either have to open them from Finder not e.g. from the File Browser in Max, but instead from the repository, and once saved, I’ll have to rebuild in order to have the new file becoming available to Max.

Is there a way that we can change this so that developers can link to the versioned JamomaMax/Jamoma folder and be able to do development on the files of this folder, with immediate availability in Max?

Thanks,
Trond
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel



------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel



------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel