Hi,

I was just looking at the file "makefile-win32" in the Csound sources
and thought it would be a nice idea to use it (with necessary changes)
instead of SCons for my Csound 5.16 build. Is there any reason why I
absolutely shouldn't use this? And why does it appear not to have been
updated in years, as the library version seems to be 5.1? Also -- for
build systems developers -- this question is slightly off-topic, but
when developing a build enviroment for a program, what precautions do
you take, if any, besides the usual process of making a build as
cross-platform as possible?

Thanks,

Adam

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The build system does many things. It configures the build to include
or exclude various features. It detects which libraries, header files,
and so on are available to the compiler. It can be configured to make
additional libraries and header files available to the compiler. It
tracks dependencies between different parts of the system.

If something in the Csound build system has not been maintained for a
long time, then it almost certainly should not be used. In software
land, "not maintained" usually means "will not work" and probably
means "we dropped it for something better."

I think you should stick with SCons until you get it to build what you
want. Keep asking questions -- we are here to help you.

If however you really insist on replicating our months of work, it
would probably be easier for you to plug all the parts into an IDE
such as QtCreator or CodeBlocks, and let that program generate the
makefile for you. That is one of the things they are supposed to do...
if Csound were not cross-platform, I think this is what I would
prefer. I've had good experiences using CodeBlocks for non-Csound
projects that included several different targets in the same project.

You will need one target in your IDE (or makefile) for every dll and
exe that you find in an installed release of Csound (except of course
for the parts you don't want). You can figure out which source files
are for which target by looking at the existing build system. A hasty
count shows about 70 targets for the Windows installer build.

You will also need to add all the third party libraries, headers,
etc., that you need to your build system. I think there are several
dozen of these now. Again, you will probably not need or want all of
them. Many of these need their own #defines and other compiler
options...

Regards,
Mike

On Mon, Feb 6, 2012 at 7:49 PM, Adam Puckett  wrote:
> Hi,
>
> I was just looking at the file "makefile-win32" in the Csound sources
> and thought it would be a nice idea to use it (with necessary changes)
> instead of SCons for my Csound 5.16 build. Is there any reason why I
> absolutely shouldn't use this? And why does it appear not to have been
> updated in years, as the library version seems to be 5.1? Also -- for
> build systems developers -- this question is slightly off-topic, but
> when developing a build enviroment for a program, what precautions do
> you take, if any, besides the usual process of making a build as
> cross-platform as possible?
>
> Thanks,
>
> Adam
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks for your answer, Mike. Another question: What are the
CMakeLists.txt files for? I think I've seen mention of CMake floating
around the list, but there isn't a makefile for CMake that I'm aware
of. I'll check the sources to see if maybe I missed something...

On 2/6/12, Michael Gogins  wrote:
> The build system does many things. It configures the build to include
> or exclude various features. It detects which libraries, header files,
> and so on are available to the compiler. It can be configured to make
> additional libraries and header files available to the compiler. It
> tracks dependencies between different parts of the system.
>
> If something in the Csound build system has not been maintained for a
> long time, then it almost certainly should not be used. In software
> land, "not maintained" usually means "will not work" and probably
> means "we dropped it for something better."
>
> I think you should stick with SCons until you get it to build what you
> want. Keep asking questions -- we are here to help you.
>
> If however you really insist on replicating our months of work, it
> would probably be easier for you to plug all the parts into an IDE
> such as QtCreator or CodeBlocks, and let that program generate the
> makefile for you. That is one of the things they are supposed to do...
> if Csound were not cross-platform, I think this is what I would
> prefer. I've had good experiences using CodeBlocks for non-Csound
> projects that included several different targets in the same project.
>
> You will need one target in your IDE (or makefile) for every dll and
> exe that you find in an installed release of Csound (except of course
> for the parts you don't want). You can figure out which source files
> are for which target by looking at the existing build system. A hasty
> count shows about 70 targets for the Windows installer build.
>
> You will also need to add all the third party libraries, headers,
> etc., that you need to your build system. I think there are several
> dozen of these now. Again, you will probably not need or want all of
> them. Many of these need their own #defines and other compiler
> options...
>
> Regards,
> Mike
>
> On Mon, Feb 6, 2012 at 7:49 PM, Adam Puckett 
> wrote:
>> Hi,
>>
>> I was just looking at the file "makefile-win32" in the Csound sources
>> and thought it would be a nice idea to use it (with necessary changes)
>> instead of SCons for my Csound 5.16 build. Is there any reason why I
>> absolutely shouldn't use this? And why does it appear not to have been
>> updated in years, as the library version seems to be 5.1? Also -- for
>> build systems developers -- this question is slightly off-topic, but
>> when developing a build enviroment for a program, what precautions do
>> you take, if any, besides the usual process of making a build as
>> cross-platform as possible?
>>
>> Thanks,
>>
>> Adam
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

CMakeLists.txt are the files Cmake uses to generate Makefiles, XCode
projects, Eclipse projects, etc.  On Windows, it should be able to be
used to create CodeBlocks projects.  I have been using CMake regularly
with make and Xcode here on OSX, and Felipe Sateler has been using it
for Linux with make.  I haven't tested in a while on Windows; it did
at one point build with make, but did not with MSVC projects.  I
believe there are some issues with Linux at the moment, but I am
looking into it now.



On Tue, Feb 7, 2012 at 2:34 AM, Adam Puckett  wrote:
> Thanks for your answer, Mike. Another question: What are the
> CMakeLists.txt files for? I think I've seen mention of CMake floating
> around the list, but there isn't a makefile for CMake that I'm aware
> of. I'll check the sources to see if maybe I missed something...
>
> On 2/6/12, Michael Gogins  wrote:
>> The build system does many things. It configures the build to include
>> or exclude various features. It detects which libraries, header files,
>> and so on are available to the compiler. It can be configured to make
>> additional libraries and header files available to the compiler. It
>> tracks dependencies between different parts of the system.
>>
>> If something in the Csound build system has not been maintained for a
>> long time, then it almost certainly should not be used. In software
>> land, "not maintained" usually means "will not work" and probably
>> means "we dropped it for something better."
>>
>> I think you should stick with SCons until you get it to build what you
>> want. Keep asking questions -- we are here to help you.
>>
>> If however you really insist on replicating our months of work, it
>> would probably be easier for you to plug all the parts into an IDE
>> such as QtCreator or CodeBlocks, and let that program generate the
>> makefile for you. That is one of the things they are supposed to do...
>> if Csound were not cross-platform, I think this is what I would
>> prefer. I've had good experiences using CodeBlocks for non-Csound
>> projects that included several different targets in the same project.
>>
>> You will need one target in your IDE (or makefile) for every dll and
>> exe that you find in an installed release of Csound (except of course
>> for the parts you don't want). You can figure out which source files
>> are for which target by looking at the existing build system. A hasty
>> count shows about 70 targets for the Windows installer build.
>>
>> You will also need to add all the third party libraries, headers,
>> etc., that you need to your build system. I think there are several
>> dozen of these now. Again, you will probably not need or want all of
>> them. Many of these need their own #defines and other compiler
>> options...
>>
>> Regards,
>> Mike
>>
>> On Mon, Feb 6, 2012 at 7:49 PM, Adam Puckett 
>> wrote:
>>> Hi,
>>>
>>> I was just looking at the file "makefile-win32" in the Csound sources
>>> and thought it would be a nice idea to use it (with necessary changes)
>>> instead of SCons for my Csound 5.16 build. Is there any reason why I
>>> absolutely shouldn't use this? And why does it appear not to have been
>>> updated in years, as the library version seems to be 5.1? Also -- for
>>> build systems developers -- this question is slightly off-topic, but
>>> when developing a build enviroment for a program, what precautions do
>>> you take, if any, besides the usual process of making a build as
>>> cross-platform as possible?
>>>
>>> Thanks,
>>>
>>> Adam
>>>
>>> ------------------------------------------------------------------------------
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net