Re: [ccmtools-devel] integration of our python binding

[<Joe...@sa...>]

>>>>> "Darrell" == Darrell Schiebel <da...@sc...> writes:

Darrell> (1) we do not want to use confix; we'd like to have an alternative  
Darrell> build option for C++ [in particular, we've been using Ant to build  
Darrell> the C++ portion of the CCMTOOLS distribution, i.e. cpp-environment  
Darrell> and wx, and Python's build system (e.g. via a setup.py file) build  
Darrell> everything that gets generated]. While we are not wedded to Ant, we  
Darrell> don't want to use confix (though this is based on our experience with  
Darrell> it which is now a few years old). Are you open to introducing another  
Darrell> C++ build option?

I guess I have to jump in here, at least to gather some (ex-) user
experience. (For the past few years I did only do this in-house at our
company; needless to say that only one use case makes for a limited
amount of scope.)

Would you mind telling me what were the troubles? A few things come to
my mind anyway if I put myself into a user's position,

* The namespace story (to make this an inherent feature rather than a
  switchable goodie was a big mistake I admit).

* The autotools, combined with Windows.

What else? I am open for flames, so don't hesitate.

Thanks,
Joerg