yade-pkg team mailing list archive

[Bruno Chareyre <bruno.chareyre@xxxxxxxxxxx>]

Hi,

I will probably not help a lot for packaging, but I'd like to keep in touch
and see if I can understand how things evolve, and maybe learn a few things.
Thank you in advance to all involved in this job.

Just a few comments :

> There are
> some scattered information on the wiki, but I was not able to follow those
> with kdevelop4 (it says, for instance, that yade is not recognized as
> executable, but that is because it is a python script and python must be
> the first argument)


IIRC, I tried to launch yade from kdevelop with python as 1st argument but
it didn't work.
It would be nice to start yade from kdev, but it is actually not a real
problem if we don't since you can always link kdev-gdb to a runing instance
of yade, as explained in the wiki. The only situation were it is annoying is
for debugging crash at startup.



> What it should include is: navigating source by tags, showing class
> definitions/declarations, automatically follow code style, run compilation
> from the IDE for release/debug version, support gdb for stepping through
> the program. Optionally, it should also integrate with bzr for commits,
> logs, diffs etc.
>

Concerning kdevelop : for browsing, there is the right-click->pick-something
trick, also displaying equivalent hotkeys for each "something" (go to
header, find definition, declaration, etc.). For gdb, there is the trick
above.
I can elaborate instructions in the wiki if something is really hard to
figure out, but most of this is covered by kdevelop documentation already.
The default (and best supported) build system in kdev is cmake, and Qt is
the tool for GUIs design (obviously).
The most annoying thing is registered attributes are not tagged, but I guess
the problem is on the ctag side rather than kdevelop (confirm?). I have to
use the "search in source*s*" (ctrl+shift+f) for those.

>
>
> 3. Port to windows. I am sorry to say that, but I keep running in people
> who will not install Yade because they do not run Linux. It would be
> possible (using some scripting and essentially compiling all dependent
> libs
> from sources) to cross-compile all that using gcc-mingw32 cross-compiler
> (I
> used to compile a wxWidgets-based program like that in the past, though it
> was much smaller).


I wanted to try the mingw approach like one year ago. I gave up when I
realised the distro contains years-old versions of most libraries (e.g.
boost), and you can nothing about it (mingw has its own repositories). Still
worth having another look, but I think msvc compilation is more feasible. It
has Qt support and other things, and it is a good software overall.
Also interesting with msvc : you can link vs. static versions of the libs,
resulting in a yade.exe that everybody can download and run without the need
to install anything else.

Cheers.

Bruno