Changing/Unifying KDevelop's CLI arguments
Aleix Pol
aleixpol at kde.org
Fri Sep 24 19:02:19 UTC 2010
On Fri, Sep 24, 2010 at 8:10 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> On 24.09.10 16:41:40, Milian Wolff wrote:
> > I want:
> >
> > ~~~~~~~~~~~~
> > $ kdevelop --help
> > Usage: kdevelop [Qt-options] [KDE-options] [options] files
> >
> > The KDevelop Integrated Development Environment
> >
> > Generic options:
> > --help Show help about options
> > --help-qt Show Qt specific options
> > --help-kde Show KDE specific options
> > --help-all Show all options
> > --author Show author information
> > -v, --version Show version information
> > --license Show license information
> > -- End of options
> >
> > Options:
> > -p <project>
> > --project <project> Url to project to load
> >
> > Arguments:
> > files Files to load
> > --debug <debugger> Start debugger, for example gdb. The binary
> that
> > should be debugged must follow - including arguments. Example:
> > kdevelop --debug gdb someapp --somearg
> > -n <name>
> > --new-session <name> Start KDevelop with a new session with the
> given
> > name.
> > -s <session>
> > --session <session> Start KDevelop and load the given
> session.
> > You can pass either hash or the name of the session.
> > -l
> > --list-sessions List available sessions and quit
> > ~~~~~~~~~~~~
>
> Great idea, what about -d for debugging? Or is that already taken by
> Qt/KDE options?
>
> Andreas
>
> --
Your reasoning powers are good, and you are a fairly good planner.
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
It would be a great feature to have indeed, I remember talking about it with
niko in berlin and there was some complexity I can't recall.
Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100924/fc1e3a6a/attachment.html>
More information about the KDevelop-devel
mailing list