Hi,
"Alan W. Irwin" <[EMAIL PROTECTED]> wrote:
> On 2006-12-11 20:42-0800 Brandon J. Van Every wrote:
...
> I don't think there are any technical issues. I have had one rpm
> packager working with our new CMake build system for PLplot, and he is
> not having too much trouble with it.
AFAIK Dirk
On 2006-12-11 20:42-0800 Brandon J. Van Every wrote:
Someone showed up on the Chicken mailing list and wants to do Debian
packaging for Chicken. I'm looking at what I need to do to support packaging
systems "in general." I've noticed several problems already:
- packages tend to duplicate th
Someone showed up on the Chicken mailing list and wants to do Debian
packaging for Chicken. I'm looking at what I need to do to support
packaging systems "in general." I've noticed several problems already:
- packages tend to duplicate the project's manifest. Often these
duplications are ma
I replaced my references to CMAKE_SOURCE_DIR and CMAKE_BINARY_DIR and
was able to get both projects to build in the same build director. My
top level basically builds a project in my src directory, and another
project in my src/Dataflow directory. However, when I run make, I get
errors like the
> IF(1)
> ELSE(1)
>FIND_PROGRAM(P_1 p_1)
>FIND_PROGRAM(P_2 p_2)
>IF(EXISTS ${P_1} AND EXISTS ${P_2} )
>ELSE(EXISTS ${P_1} AND EXISTS ${P_2} )
>ENDIF(EXISTS ${P_1} AND EXISTS ${P_2} )
> ENDIF(1)
So :) This is effectively an implementation bug. I suspect it can be fixed
reasonabl
On 12/9/06, Axel Roebel <[EMAIL PROTECTED]> wrote:
Tristan Carel wrote:
> Hi Swig lovers,
>
> Axel had the great idea to use the -swiglib option in order to improve
> the module's efficiency to properly fill the prerequesites variables.
> I guess it is the perfect example of using a tool to perf
