[Scons-users] Question about scons

[Guillaume Anciaux]

Hello,

thank you for your answer. Indeed, I had a look at the Tools on my
debian. When I look at the list from following your link below, what I
see is mainly build/compilers but no 'configure' variable for projects like:

- petsc
- blas
- lapack
- mumps
- fftw
- boost
- gsl
- MPI (openmpi, mpich, mpich2, etc...)

I do not say that these are complicated. Most of them are not (PETSc is
a counter-example...).  But even searching on the web (very quickly I
admit), I cannot find scons tools. I can tell you that the same exercise
would be successful in CMake.

What I mean is that a central place for storing these scripts (in CMake
they are part of the main release) would be extremely valuable to give
the feeling that everything is easy and just focus on your own files and
not the libraries and includes of others.

This is what I would motivate by a 'central repo'. Again I am very new,
so don't judge me badly if I say wrong things.

Thanks again for your answer.

Best.

Guillaume


On 02/09/2016 07:18 PM, Gary Granger wrote:
> Hello Guillaume,
>
> I have not used cmake, but I took a quick look at the CMake
> find_package documentation along with some of the Find<package>.cmake
> modules.  They look like SCons "tools" to me.  A SCons tool is a
> python function, module, or package which can be applied to an
> Environment to add construction variables and methods (Builders).  The
> core SCons distribution already contains a repository of some
> important tools, you can see them under the SCons package in the
> SCons/Tool directory.  Some tools are quite simple to write, some are
> more complicated.  My impression is that the core tools are mostly
> compilers, but there are many more tools developed externally, some of
> which are listed on this wiki page:
>
>     https://bitbucket.org/scons/scons/wiki/ToolsIndex
>
> Those are the closest things I know of to a repository for tools. 
> Usually if I need a new tool, I just search for it on the web or write
> it.  Custom tools can be integrated with your source tree or installed
> alongside SCons, as explained in the SCons documentation.
>
> It could be an interesting exercise to parse or convert (ie "export") 
> the CMake package modules for SCons, but I suspect there are already
> SCons tools for many of them.  If you can't find a particular tool you
> need, then I suppose this is a good place to ask about it.  If CMake
> has a package that SCons doesn't, it may not be hard to convert the
> CMake package manually.  SCons already supports parsing of pkg-config
> scripts.
>
> HTH,
> Gary
>
> On 02/09/2016 09:10 AM, Guillaume Anciaux wrote:
>> Dear Scons developers and users,
>>
>> I am new to the topic, and find it great that the Python language is the
>> support of a build tool.
>>
>> However, I used to manage a large project with CMake and was ready to
>> change from the crappy language that CMake is.
>>
>> However something that is extremely nice is the database of
>> 'find_package' routines that helps in finding default software.
>>
>> I searched a little but found no such thing for Scons ? am I right ?
>>
>> If so, is it a naive though to:
>>
>> - start such a repo ?
>> - write an exporter from the CMake format to benefit from the long list
>> of packages already supported ?
>>
>> Thanks a lot for this nice project,
>>
>> thanks for your answers !
>>
>
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20160210/1c07693c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1513 bytes
Desc: OpenPGP digital signature
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20160210/1c07693c/attachment.pgp>