Sponsored Content
Full Discussion: Motif - RedHat 7.3
Top Forums Programming Motif - RedHat 7.3 Post 22039 by CreamHarry on Monday 27th of May 2002 12:04:16 PM
Old 05-27-2002
Motif - RedHat 7.3

Can somebody help me...
I have insalled RedHat 7.3 on my computer
and there is motif 2.x and i want to compile a cource code but it doesn't work it says
Xm/PushB.h not found..something like that..
I'm trying like this :
gcc -o x x.c -lXm -lXt -lX11

pleas help me
 

10 More Discussions You Might Find Interesting

1. Programming

Motif resources

I am very glad to be a member of you. where can i look for the resource programe examples about motif? please help me!Thanks a lot. (3 Replies)
Discussion started by: q30
3 Replies

2. Programming

Motif

Do you think that Motif programming is old...should I learn it... (3 Replies)
Discussion started by: CreamHarry
3 Replies

3. Programming

motif help

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)
Discussion started by: qqq
0 Replies

4. Shell Programming and Scripting

Dtksh + Motif newb

I have a script that creates a Form and multiple textfield, text, and label widgets in which the user inputs data, and submits it to be organized and formatted accordingly.... Some of the information that the user is manually adding comes from a text area in a separate application. Is it... (0 Replies)
Discussion started by: insamniac
0 Replies

5. AIX

Motif on AIX and SWT

hi all, I've written a GUI application in Eclipse using SWT. It's running fine on linux(which uses GTK on x86). But when I ran the same application on AIX(which uses Motif on PPC), the GUI part is suffering. :-( The checkboxes are looking very small(like tiny dots on screen!) , spinners are... (4 Replies)
Discussion started by: v_rathor
4 Replies

6. HP-UX

motif reqired for hp-ux 11.11

hello everyone, where can i download motif compatible with HP-UX 11.11.which motif version i have to use. can i use openmotif 2.3 for HP-UX 11.11. pls somebody suggest a solution .it's very urgent. any help appreciated. with regards, Srini (0 Replies)
Discussion started by: mannam srinivas
0 Replies

7. Solaris

Motif 1.2 support on Solaris 10

Hello, I used to compile and link the code on Solaris 6 using Motif 1.2 (that used to come as part of Operating System) I would like to use the same version of Motif 1.2 for compilation and linking on Solaris 10. But Solaris 10 has Motif 2.1.0 as default. Is Motif 1.2 supported on... (0 Replies)
Discussion started by: shafi2all
0 Replies

8. Solaris

Motif 2.1 migration from Motif 1.2

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)
Discussion started by: shafi2all
0 Replies

9. Programming

Change font in Motif

Does anyone know how to change the font size into a larger one, in a basic Motif application? (1 Reply)
Discussion started by: JenniferKuiper
1 Replies

10. Programming

Motif Application will not refresh

I have a Motif Application created with XtVaAppInitialize. I have two field widgets, created with XmCreateTextField. Now when I programmatically change the data in any of the two fields, the widgets don't get refreshed, only after a mouse over. I have tried anything, from including the "xrefresh"... (4 Replies)
Discussion started by: JenniferKuiper
4 Replies
ATTILA(1)						  Alliance - attila User's Manual						 ATTILA(1)

NAME
attila - A Tool Installer SYNOPSIS
attila [ -h ] [ -S ] [ -U ] [ -F ] [ -A ] [ --help ] [ --ssh ] [ --user ] [ --asim ] [ --prefix=INSTALL_DIR ] [ --builddir=BUILD_DIR ] --tool=name1 [ --tool=name2... ] [ -c- configure_arg1 [ configure_arg2 ... ] ] [ -m- make_arg1 [ make_arg2... ] ] DESCRIPTION
attila automates the process of compiling and installing one or more Alliance tools. The tool can be installed either in the user's account (during the devellopment stage) or in the Alliance system wide tree (for instance /asim/alliance) when a new version is made avalaible to all. attila proceed with the following steps : 1. Checks if the sources of tools are present in the user's account. If not, check them out from the Alliance CVS tree. Note that you must have access to it. 2. In case of --asim or --full installations, attila will fork itself on one Linux computer (currently bip) and on one Solaris computer (beny). As to connect on thoses computer it will uses rsh so you must setup your ~/.rhosts to access them whithout passwords. You also can uses ssh (but the procedure to allow automatic login is more complicated). 3. Run autostuff for the tool in the ~/alliance/src directory. 4. Run configure in the build directory (see below). 5. Install the tool in the local install directory (see below) or in the system-wide Alliance directory rooted under /asim/alliance. After an --asim install: the build directory tree of the tool will be removed to avoid messing with further local installations. DIRECTORY STRUCTURE attila relies on the following tree structure : (all paths below are given relative to the user's home directory) o ~/alliance/src where the tools sources are to be found. o ~/alliance/Linux/build/$TOOL : the top directory under which the tool will be compiled for Linux. This is where the configure script will be run. o ~/alliance/Linux/install : the top of the install tree when the tool is compiled locally for Linux. Under this directory you will found (at least) : ./bin, ./lib and ./include. o ~/alliance/Solaris/build/$TOOL : the tool's build directory for Solaris. o ~/alliance/Solaris/install : top of the local install tree for Solaris. CVS CHECKOUT If the sources of the requested tool(s) are not found under ~/alliance/src/ attila will try to check them out. So, as says above, you must have access rights to the Alliance CVS tree. In addition to the tool(s) sources, it will also checks for the minimal set of files needed for configure to run. As for now : o autostuff o alliance.m4 o motif.m4 o Makefile.am GUESSING CVSROOT The root of the CVS tree will be set according to the following rules : 1. Uses the user's environment variable CVSROOT if sets. 2. Uses the attila default value sets in attila.conf (variable ATTILA_CVSROOT). GUESSING ALLIANCE_TOP The root of the Alliance installed distribution tree will be set according to the following rules : 1. Uses the user's environment variable ALLIANCE_TOP if sets. 2. Uses the attila default value sets in attila itself (variable ATTILA_ALLIANCE_TOP). ALLIANCE_TOP: is set in attila itself because its value is a prerequisite to load the configuration file attila.conf which is in the directory $ALLIANCE_TOP/etc/. ARGUMENTS
attila accepts the followings arguments : o -h, --help : print help. o -S, --ssh : uses ssh instead of rsh to connect to the remote computers (in case of --asim or --full). o -U, --user : perform a local installation. o -F, --full : install for all avalaibles architectures (currently Linux and Solaris). o -A, --asim : install in the system-wide directory (/asim/alliance). o --prefix=INSTALL_DIR : override the default installation directory. o --builddir=BUILD_DIR : override the default building directory. o --tool=name1 : name of the tool to be installed. o -c- configure_arg1 : all arguments following -c- (until a -m- is encountered) are passed as is to the subsequent call to configure. For example, if you want to first use your local libraries, give --enable-devel. If you want to link or install dynamic libraries, give --enable-alc-shared for alliance libraries and give --enable-shared for other libraries. o -m- make_arg1 : all arguments following -m- are passed as is to the subsequent call to make. If no -m- argument is given, then install is assumed. If you want to completly uninstall a tool and clean it's build directory you can pass uninstall clean CONFIGURATION FILE ATTILA.CONF The configuration file is located in $ALLIANCE_TOP/etc. This file is to be read by the sh shell. It sets up the following variables : o LINUX_TARGET : the computer where to compile for the Linux architecture (default bip). o LINUX_CC : the name or full path to to the C compiler for Linux system (default gcc3). o LINUX_CXX : the name or full path to to the C++ compiler for Linux system (default g++3). o SOLARIS_TARGET : the computer where to compile for the Solaris architecture (default beny). o SOLARIS_CC : the name or full path to to the C compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o SOLARIS_CXX : the name or full path to to the C++ compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o ATTILA_CVSROOT : the root of the Alliance CVS tree (default /users/outil/alliance/cvsroot). o CVS_STARTUP_FILES : the minimal set of files needed to run configure. EXAMPLES
Compile & install nero tool on the local computer (must be either a Linux or a Solaris one) : $ attila --tool=nero Compile & install nero tool for all architectures (currently only Linux and Solaris are supported) : $ attila --full --tool=nero Compile & install nero tool in the system-wide directory (a new version for everyone to use) : $ attila --asim --tool=nero Compile & install mbk then genlib (the order is significant) in a row for a local install on the current computer : $ attila --tool=mbk --tool=genlib Compile nero tool and link it against the locally installed libraries (if any). $ attila --tool=nero -c- --enable-devel Remove poire tool from the system-wide tree. (poire is the old name of nero). $ attila --asim --tool=poire -m- uninstall ASIM
/LIP6 13 October 2002 ATTILA(1)
All times are GMT -4. The time now is 12:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy