Compiler Qucs (avec Qt) sous Mac OS X
overmac
Membre
Bonjour à tous,
je suis un utilisateur du prometteur logiciel [URL=http://"http://qucs.sourceforge.net/"]Qucs[/URL] (soft de simulation de circuits électroniques) qui à été conçu sur Qt. Donc, ce soft peut fonctionner sur différentes plates-formes dont Mac OS X.
Seulement, le portage sur des plates-formes autres que Linux ne se fait pas par l'équipe en charge du développement de Qucs, mais par des volontaires qui mettent à disposition leurs temps pour cette tâche. La personne qui s'occupe du portage pour Mac (qui se nomme [URL=http://"http://naranja.umh.es/~atg/software-qt3.html"]Markus[/URL]) s'est arrêter à la version 0.0.8 (actuellement on en est à la [URL=http://"http://prdownloads.sourceforge.net/qucs/qucs-0.0.10.tar.gz?download"]0.0.10[/URL]) et semble ne plus pouvoir continuer l'aventure faute de temps :
Pour compiler ce logiciel, il faut Qt version 3 et donc installer la version minimum 3.3.6, pour mac. Elle se trouver ici : [URL=http://"ftp://ftp.trolltech.com/qt/source/"]previous version[/URL]
On peut lire dans le fichier d'installation :
Après presque toute une nuit mais, Qt est installé :
Ensuite, je place le dossier qucs-0.0.10 est sur mon bureau. Donc depuis le Terminal, je vais dans ce dossier puis je tape ./configure comme écrit dans le fichier INSTALL. Et j'obtiens :
Si j'ai bien compris, en Unix, le linker va aller chercher les librairies à linker (.a pour les statiques et .so pour les dynamiques) dans le répertoire pointé par LD_LIBRARY_PATH. Mais sous Mac OSX, Apple a nommé ses libraries dynamiques .dylib et du coup a ajouté une variable DYLIB_LIBRARY_PATH. Et quand je tape echo $DYLD_LIBRARY_PATH dans le Terminal, je vois bien le chemin /Developer/qt/lib.
Quelqu'un aurait-il une idée ? Car je n'arrive plus à avancer.
D'avance merci...
je suis un utilisateur du prometteur logiciel [URL=http://"http://qucs.sourceforge.net/"]Qucs[/URL] (soft de simulation de circuits électroniques) qui à été conçu sur Qt. Donc, ce soft peut fonctionner sur différentes plates-formes dont Mac OS X.
Seulement, le portage sur des plates-formes autres que Linux ne se fait pas par l'équipe en charge du développement de Qucs, mais par des volontaires qui mettent à disposition leurs temps pour cette tâche. La personne qui s'occupe du portage pour Mac (qui se nomme [URL=http://"http://naranja.umh.es/~atg/software-qt3.html"]Markus[/URL]) s'est arrêter à la version 0.0.8 (actuellement on en est à la [URL=http://"http://prdownloads.sourceforge.net/qucs/qucs-0.0.10.tar.gz?download"]0.0.10[/URL]) et semble ne plus pouvoir continuer l'aventure faute de temps :
Hello,
thanks for your email. ATG is a leisure time project so there is
usually at least some delay before a new version of any of the
programs appears on it. Related to the page I'm actually
restructuring several aspects of it including how installers are
provided, feedback, etc. These changes will be revealed starting from
the next weekend.
There are still some technical issues I have to address mainly how to
create comfortable and somewhat elegant installers for both PPC- and
Intel-based Macs. This "eats" much the spare time I can attribute to
ATG, even much more then creating the actual installer, so the
easiest way might be for you to compile the latest qucs *or any other
newer version of any of the programs on ATG* by yourself.
Due to the large amount of traffic the page is sometimes generating
I'm not even sure wether I'll keep *and can keep* the actual
distribution scheme. I'll hope to solve most technical issues till
this sunday. If everything goes well I'll then go and update every
day contents, images, RSS-feed generation and one of the installers,
etc....
Because ATG is a "one-man-for-fun-project" I'm sorry but I can't
offer any, more specific date regarding for example an update to
qucs. It might show up sooner or later... *actually regarding qucs:
I'm trying to include the digital simulation stuff working on MacOSX
(Intel & PCC), but there are some issues. I decided not to update
the installer during the last weeks simply because of this, and this
time I'll presumably not do it until I solved these issues (which
will take some time because I received several emails with request
regarding other programs).*
So for the moment I'm sorry. Cheers,
Markus
Pour compiler ce logiciel, il faut Qt version 3 et donc installer la version minimum 3.3.6, pour mac. Elle se trouver ici : [URL=http://"ftp://ftp.trolltech.com/qt/source/"]previous version[/URL]
On peut lire dans le fichier d'installation :
INSTALLING Qt/Mac Version 3.3.6 (for Mac OS X)
1. Unpack the archive if you have not done so already:
cd /Developer
gnutar xzvf Full_Path_to_Directory_You_Unpacked_To/qt-mac-free-3.3.6.tar.gz
This creates the directory /Developer/qt-mac-free-3.3.6 containing the
files from the main archive.
Rename qt-mac-free-3.3.6 to qt (or make a symlink):
mv qt-mac-free-3.3.6 qt
The rest of this file assumes that Qt is unpacked in /Developer/qt.
2. Set some environment variables in the file .login (or .profile or
something else depending on your shell) in your home directory.
Create this file if it is not already there. You can check your shell
by typing:
finger Your_Login
The variables that you must set are:
QTDIR - wherever you installed Qt
PATH - to locate the moc program and other Qt tools
DYLD_LIBRARY_PATH - for the shared Qt library
This is done like this:
In .login (in case your shell is csh or tcsh), add the following lines:
setenv QTDIR /Developer/qt
setenv PATH $QTDIR/bin:$PATH
setenv DYLD_LIBRARY_PATH $QTDIR/lib:$DYLD_LIBRARY_PATH
***************************WARNING**************** **************
* Some versions of tcsh do not understand the expansion of empty
* variables. If you experience any error messages with the above
* instructions, you may want to replace them with:
*
* setenv QTDIR /Developer/qt
* setenv PATH $QTDIR/bin:$PATH
* setenv DYLD_LIBRARY_PATH $QTDIR/lib
In .profile (if your shell is bash), add the following lines:
QTDIR=/Developer/qt
PATH=$QTDIR/bin:$PATH
DYLD_LIBRARY_PATH=$QTDIR/lib:$DYLD_LIBRARY_PATH
export QTDIR PATH DYLD_LIBRARY_PATH
If you use a different shell, please modify your environment variables
accordingly.
After you have done this, you will need to login again, or re-source the
profile before continuing, so that $QTDIR, $PATH, and $DYLD_LIBRARY_PATH
are set. Without these the installation will halt with an error message.
3. Make a symbolic link from $QTDIR/doc/man to $QTDIR/man by typing the following:
ln -s $QTDIR/doc/man $QTDIR/man
This will give you the man pages for the commandline Qt programs.
4. If you have the commercial edition of Qt, install your license
file as $HOME/.qt-license.
5. Building.
This step compiles the Qt library, and builds the example programs,
the tutorial, and the tools (e.g. Qt Designer, etc.).
Type:
cd $QTDIR
./configure
This will configure the Qt library for your machine. Run ./configure -help
to get a list of configuration options.
To create the library and compile all the examples and the
tutorial, type:
/usr/bin/make
If your platform or compiler is not supported, please contact us at
qt-bugs@trolltech.com so that we can assist you. If it is supported
but you have problems, see http://www.trolltech.com/platforms/ for
information on known issues.
6. Launching Qt applications from the Finder.
If you built Qt using the -static option, your executables will contain the
Qt library and can be run from Finder automatically. Otherwise, your
executables will need to use the Qt library on your system. You can achieve
this by using symbolic links.
We recommend making these symbolic links (if you have configured Qt with
-thread [ie threading enabled], please change the libqt below with
libqt-mt):
ln -sf $QTDIR/lib/libqt.3.dylib /usr/lib
ln -sf $QTDIR/lib/libqui.1.dylib /usr/lib
You may need to have 'administrator' access to do this, (in which
case, precede each command with 'sudo', e.g. 'sudo ln -s ...'). If
you use sudo you'll be prompted for your password.
If you do not have administrator access, or you would prefer to do
a user install (rather than system install) of the libraries you
can do (if you have configured Qt with -thread [ie threading enabled],
please change the libqt below with libqt-mt):
ln -sf $QTDIR/lib/libqt.3.dylib $HOME/lib
ln -sf $QTDIR/lib/libqui.1.dylib $HOME/lib
Note: you can also achieve similar functionality by adding your
DYLD_LIBRARY_PATH to the GUI's environment.
That's all! Qt is now installed. Qt's documentation can be read with
Qt Assistant or by any web browser; the contents page is:
$QTDIR/doc/html/index.html
See the PLATFORM file for details pertaining to your environment.
Après presque toute une nuit mais, Qt est installé :
The Qt library is now built in ./lib
The Qt examples are built in the directories in ./examples
The Qt tutorials are built in the directories in ./tutorial
Enjoy! - the Trolltech team
Ensuite, je place le dossier qucs-0.0.10 est sur mon bureau. Donc depuis le Terminal, je vais dans ce dossier puis je tape ./configure comme écrit dans le fichier INSTALL. Et j'obtiens :
power-mac-g4-de-overmac-overmac:~/Desktop/qucs-0.0.10 overmac$ ./configure<br />checking build system type... powerpc-apple-darwin8.7.0<br />checking host system type... powerpc-apple-darwin8.7.0<br />checking target system type... powerpc-apple-darwin8.7.0<br />checking for a BSD-compatible install... /usr/bin/install -c<br />checking whether build environment is sane... yes<br />checking for gawk... no<br />checking for mawk... no<br />checking for nawk... no<br />checking for awk... awk<br />checking whether make sets $(MAKE)... yes<br />checking whether to enable maintainer-specific portions of Makefiles... no<br />checking for g++... g++<br />checking for C++ compiler default output file name... a.out<br />checking whether the C++ compiler works... yes<br />checking whether we are cross compiling... no<br />checking for suffix of executables... <br />checking for suffix of object files... o<br />checking whether we are using the GNU C++ compiler... yes<br />checking whether g++ accepts -g... yes<br />checking for style of include used by make... GNU<br />checking dependency style of g++... gcc3<br />checking for gcc... gcc<br />checking whether we are using the GNU C compiler... yes<br />checking whether gcc accepts -g... yes<br />checking for gcc option to accept ANSI C... none needed<br />checking dependency style of gcc... gcc3<br />checking for ranlib... ranlib<br />checking for ar... ar<br /><br /> The qucs package has never been compiled or run on this platform.<br /> Please send an email to <qucs-devel@lists.sourceforge.net> including your<br /> compiler and Qt version and whether it worked correctly or not. The<br /> 'powerpc-apple-darwin8.7.0' line will then be added to the PLATFORMS file included<br /> in this package.<br /><br />checking for lrelease... /Developer/qt/bin/lrelease<br />checking for lupdate... /Developer/qt/bin/lupdate<br />checking for moc... /Developer/qt/bin/moc<br />checking for uic... /Developer/qt/bin/uic<br />checking how to run the C preprocessor... gcc -E<br />checking for X... libraries /usr/X11R6/lib, headers in standard search path<br />checking for gethostbyname... yes<br />checking for connect... yes<br />checking for remove... yes<br />checking for shmat... yes<br />checking for IceConnectionNumber in -lICE... yes<br />checking for Qt headers... found in /Developer/qt/include<br />checking for Qt... 3 (multi-threaded)<br />checking for Qt library... configure: error: not found
Si j'ai bien compris, en Unix, le linker va aller chercher les librairies à linker (.a pour les statiques et .so pour les dynamiques) dans le répertoire pointé par LD_LIBRARY_PATH. Mais sous Mac OSX, Apple a nommé ses libraries dynamiques .dylib et du coup a ajouté une variable DYLIB_LIBRARY_PATH. Et quand je tape echo $DYLD_LIBRARY_PATH dans le Terminal, je vois bien le chemin /Developer/qt/lib.
Quelqu'un aurait-il une idée ? Car je n'arrive plus à avancer.
D'avance merci...
Connectez-vous ou Inscrivez-vous pour répondre.