MOTIF GUI PROGRAMMING !
Hi there. I am a MOTIF GUI Programmer in C language.
After a longer break i have problems with the GCC compiling.
my MOTIF file is named winstack.c
I have the follow code
The compilation runs good.
But no executable LINUX FILE is created. except a file named newprogram.
The properties of the file in the context menue is "shared library" not "executable".
Thats my problem.
From commandline is no problem with ./newprogram. A GUI Windows is opening.
How about a real linux exe to start with one click in file explorer ???
Kindly Regards
SM
I am a newbie to the *nix developer community, and was wondering if anyone has any good links on the subject of GUI programming in the X environment. Any suggestion is welcome =). (2 Replies)
Hi everyone, I am new in motif programming and I want to learn how to program it. I use Fedora core 3 and every time I compile the program, there are always some errors appear. One of the errors said that I do not have the Xm/xxxx.h However, I do not know precisely how to install header files. I... (0 Replies)
Hello all,
1) I want to have a GUI application that will call Unix shell scripts,
2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix.
That is for example.
If a is windows gui (... (1 Reply)
An application was getting built using Motif 1.2 that used come along Solaris 6 OS for compiling and linking. Application is run using Motif 2.1 on Solaris 10 and it is working fine.
Application compilation and linking is working fine on Solaris 10 with Motif 2.1.0 but running the application... (0 Replies)
Hi there ,
i am interesting in MOTIF programming.
One question :
Is it right that in Motif GUI programming the actions are automaticly transformed and networked to other clients over the internet without network programming necessary ?
Are the commands automatic transformed by the X11... (4 Replies)
Hi ,
wanna learn native GUI programming in Unix-Linux instead of Gtk and Qt.
No problem. You don't need a cross platform Gui toolkit like Gtk and Qt.
And the code and syntax is also not more or less than others.
Check out this code for a simple mainwindow for your application that is openend in... (0 Replies)
Motif GUI example. Unix executable ready.
Hi ,
i have attached my executable GUI example file in form of a .gz file.
please gunzip file before.
May i ask you for check it out that it is running on your machine ?
You should have "Motif" package installed.
when you klick the unix executable... (4 Replies)
Discussion started by: Sennenmut
4 Replies
LEARN ABOUT DEBIAN
buildapp
BUILDAPP(1) User Commands BUILDAPP(1)NAME
buildapp - application to create common lisp images
SYNOPSIS
buildapp --output OUTPUT-FILE [--flag1 value1 ...]
DESCRIPTION
Required flags:
--output OUTPUT-FILE
Use OUTPUT-FILE as the name of the executable to create
Entry-point flags:
--entry NAME
Use the function identified by NAME as the executable's toplevel function. Called with SB-EXT:*POSIX-ARGV* as its only argument. If
NAME has a colon, it is treated as a package separator, otherwise CL-USER is the implied package.
--dispatched-entry DNAME
Specify one possible entry function, depending on the name of the file that is used to start the application. The syntax of DNAME is
APPLICATION-NAME/ENTRY-NAME. If the name used to start the executable matches APPLICATION-NAME, use ENTRY-NAME as the entry point.
This can be used to choose one of many possible entry points by e.g. symlinking names to the application executable. If APPLICA-
TION-NAME is empty, the specified ENTRY-NAME is used as a default if no other application names match. There may be any number of
dispatched entry points, but only one default.
Action flags:
--load FILE
Load FILE. CL:*PACKAGE* is bound to the CL-USER package before loading
--load-system NAME
Load an ASDF system identified by NAME
--require NAME
Use CL:REQUIRE to load NAME
--eval CODE
Use CL:EVAL to evaulate CODE. The code is read with CL:READ-FROM-STRING in the CL-USER package
There may be any number of load/load-system/require/eval flags. Each is executed in command-line order before creating an executable.
Load path flags:
--load-path DIRECTORY
When handling a --load, search DIRECTORY for files to load
--asdf-path DIRECTORY
When handling a --load-system, search DIRECTORY for ASDF system files to load
--asdf-tree DIRECTORY
When handling a --load-system, search DIRECTORY and all its subdirectories for ASDF system files to load
There may be any number of load-path/asdf-path/asdf-tree flags. asdf-path arguments take precedence over asdf-tree arguments.
Other flags:
--help Show this usage message
--logfile FILE
Log compilation and load output to FILE
--sbcl PATH-TO-SBCL
Use PATH-TO-SBCL instead of the sbcl program found in your PATH environment variable
For the latest documentation, see http://www.xach.com/lisp/buildapp/
buildapp 1.1 July 2010 BUILDAPP(1)