Re: New linux programmer

ta0kira@xxxxxxxxx writes:
On Aug 30, 1:30 am, Joshua Baldus <baldu...@xxxxxxxxx> wrote:
Hey all,
I'm not entirely new to c++ programming, but I've decided to switch focus to
linux based development. It's a completely new environment for me - I'm
used to Visual Studio - so I decided to try KDevelop for a starting point.
Unfortunately, it seems to require some serious understanding of linux
development environments - I can't even compile a basic Qt hello world
app - /bin/sh qmake not found. I checked the QT_DIR variable and it points
to the Qt directory fine, but ... shrug

Honestly, KDevelop is a terrible way to learn Linux programming.
Unlike Windows, the Linux API (if there is one) doesn't correlate to
any sort of GUI.

'Linux' is an operating system kernel and this kernel is intended to
conform to the relevant POSIX/ UNIX(*) standards wrt OS interfaces,
insofar they apply to the kernel. And this is 'an API'.

[...]

If you're going to go with the text editor method, you'll want to
learn to use makefiles. Once you get a good handle on makefiles, you
should also learn automake, autoconf, and libtool. Those will allow
you to build otherwise-portable programs on other Unix systems.

It should be noted that this is the direct opposite of the purpose of
Gnu autoblurdybloop, which originally was to provide a framework for
configuring the build of applications ported to various operating
environments automatically for the one presently used to build them.

But this is kind-of pointless, because in the end, it means you will
be porting the build system to the new environment instead of the
application. And autconf is confusing, sparseley documented and
usually incompatible with itself accross different releases (eg I need
to keep a 2.53 version around to be able to build the MIT Kerberos
code 'we' use). Insofar you care for the mental sanity of people that
may actually have or want to use your code in an environment which
significantly differs from the one you are using avoid auto*.

If somebody has an actual use for it (ie needs modifications the the
one platform build system which are complicated enough that a
buildsystem building framework makes sense) he or she can always add
support for it.

It's a long process, and to be blunt, you won't be a decent Linux
programmer unless you dive deep into the glibc documentation, learn to
write makefiles by hand, and can write a large program (sans GUI) with
multiple libraries without going near an IDE.

Is this supposed to be complicated?
.

Relevant Pages

  • New linux programmer
    ... I'm not entirely new to c++ programming, but I've decided to switch focus to ... it seems to require some serious understanding of linux ... Basically I'm looking for a programming environment for xwindows (openSuSE ... as long as I can learn the basics of the linux dev ...
    (comp.os.linux.development.apps)
  • Re: New linux programmer
    ... It's a completely new environment for me - I'm ... it seems to require some serious understanding of linux ... KDevelop is a terrible way to learn Linux programming. ... with the occasional GUI wrapper for convenience. ...
    (comp.os.linux.development.apps)
  • need a user friendly programming environment.
    ... hi can anyone tell of an excellent user friendly programming ... environment for linux just like the visual basic and visual c++ in ... windows. ...
    (comp.os.linux.questions)
  • need a user friendly programming environment.
    ... hi can anyone tell of an excellent user friendly programming ... environment for linux just like the visual basic and visual c++ in ... windows. ...
    (comp.os.linux)
  • Re: Why do so many people love Teas Instruments?
    ... that almost every modern programming language ... What you described is some "improvements" to the algebra, ... different calculators will produce different results depending on how ... She lived with Linux for a few weeks, ...
    (comp.sys.hp48)