Graphic Interface not available when running simulation - macos

I'm getting this error when running the configure file:
configure: error: Cannot build Qt apps, probably due to missing or too
old Qt packages. Make sure Qt development packages are installed and
newer than Qt 5.4. You can disable Qtenv by setting the WITH_QTENV
variable to "no" in configure.user
I've installed Qt5 and also added the path to the paths file.
My Qt version is 5.15.0 and my MacOS is Catalina (10.15.5 (19F101)).
Probably qmake is not able to build the Qt interfaces but I couldn't make it do it.

I think you're misunderstanding for OS support bit. macOS (After High Sierra version) is only use 64bit (x86_64). If you want to know your macOS support bit information, you can execute "uname -a" command in terminal.
i386: 32bit
x86_64: 64bit
I hope this has been useful. :D

It seems that my OS version is 32 bits and Qt5 is 64 bits. Since some of the binaries come in the 64 bits flavor, I was not able to use it with omnet++ 5.6.
I installed omnet++ version 5.0, but the program wouldn't run.
So I went back to omnet++ 5.6 and instead of using Qt, I compiled with tcl/tk and that worked for me.

Related

Installing OMNeT++ on M1 MacBook

Followed instructions given in https://doc.omnetpp.org/omnetpp/InstallGuide.pdf
OMNeT++ Version - omnetpp-5.6.2
Device - MacBook Air M1 (MacOS Big Sur Version 11.4)
Encountered the following problems.
$. setenv -> didn't work (worked after replacing "." with "source")
$./configure -> gives the following error.
configure: error: Qtenv cannot find qmake -- maybe it is not in the PATH or has some exotic name (tested names were: qmake qmake-qt5 qmake5) - disabling Qtenv. You can try setting the QT_PATH variable in configure.user to a valid location
$ make -> gives the following error.
Makefile:54: Makefile.inc: No such file or directory
make: *** No rule to make target `Makefile.inc'. Stop.
Is it possible to get OMNeT++ working on M1 Macs? Any help would be greatly appreciated.
Thanks in advance.
There is no native support for M1 processors, especially because omnet++ 5.6 was released way before the M1 release, but you can run omnet with Rosetta2 in x86_64 mode. You would still get pretty decent performance. With x86_64 emulation I measured similar performance like on my last year high end AMD laptop. Native mode would give you a 25% boost compared to that.
To turn on the emulation for a shell window, start a new shell with
$ arch -x86_64 /bin/zsh --login
and then continue in that shell with
$ source setenv
$ ./configure
$ make
run everything from that shell window (as usual).
NOTE: OMNeT++ 5.6 relies on the system-wide installed JRE to run the IDE. That may NOT be present on your system if you are running on ARM. OMNeT++ 6 and 5.7 comes with a built-in private JRE, so the IDE should work with those versions also in intel emulation mode.
ps: OMNeT++ 6 may get native M1 support (this depends on the availability of some dependencies (JavaVM, Qt etc.). I'm also considering an ARM based docker image, that would allow running at native performance (as long as you have an XServer installed).

How to install nvcc on macOS catalina 10.15.7 without GPU?

When run:
which nvcc
It says:
nvcc not found
And I did not found clear guide to install nvcc,on macOS catalina 10.15.7.
Because I am trying to run https://github.com/jugg1024/Text-Detection-with-FRCN.git. But on cammand:
make -j16 && make pycaffe:
From here:
It gives this error:
Thats why i do need nvcc installation.
Any assistance you can provide would be greatly appreciated!
Since CUDA 11.0, macOS is not a supported environment for CUDA.
The last supported environment was based on CUDA 10.2 (see here) and a macOS version of 10.13.x
There has never been a supported nvcc install, CUDA install, or CUDA version for macOS 10.15.x
If you don't have a CUDA-capable GPU in your mac, it's not clear why you would want to install nvcc or CUDA. They could possibly be used to build code, but that code wouldn't be runnable on that machine.
If you do have a CUDA capable GPU in your mac, you would want to follow the above linked instructions carefully, noting carefully the machine requirements, such as supported macOS version. CUDA 10.2 would be the latest/last version of CUDA you could install on that mac.

How to minimize install of Qt for using PyQt on MacOS?

I was trying to install PyQt on my MacOS. With SIP installed, an error occurred when python3 PyQt-gpl-5.4/configure.py inputted:
Error: Use the --qmake argument to explicitly specify a working Qt qmake.
It seems that Qt should be installed before PyQt. There're many optional components in the installation of Qt:
-Qt 5.4
--clang 64-bit
--source components
---Add-Ons
---Essentials
--.....
Which components should I choose for installing qmake??
qmake is the executable that is included with any version of the qt libraries; and there is a different version of qmake for each compiler the Qt Libraries are built with/against. On a mac, and for building projects that run on OSX, you will probably want clang x64. And you will find qmake under ~/Qt/5.x/clang_64/bin It will also install qt creator (I don't think you can uncheck it), but you don't need all the extras besides that.
Building with qmake often needs XCode installed and the Command Line Tools (CLT) to use its included compiler. With Python, you probably won't need the compiler, unless you need to build some of its libraries.
Hope that helps.

Installing openCV on Lion OS 10.7.4 Xcode 4.3.2

I'm trying to install openCV on university's iMac,
but the problem is our university's network is so strict.
and I couldn't install openCV using MacPorts.
I tried google to look for a way to install but it all failed
i guess because it is kind of old ways and because my network is so strict.
So if anybody knows a way that I can download a ready framework with how to use it inside
Xcode. or at least a framework with how to install it to work with Xcode.
or a way to download from the source and compile it then install it in Xcode
please.
Because I tried the cmake way and I still have no luck to get it work.
thanks in advance.
sources I used:
http://salemsayed.me/?p=240
http://opencv.willowgarage.com/wiki/InstallGuide
http://opencv.willowgarage.com/wiki/Mac_OS_X_OpenCV_Port
http://www.ient.rwth-aachen.de/cms/software/opencv/
I'm using Lion + Xcode 4.x branch, with OpenCV svn trunk. Everything works fine. You have to install cmake first, then get the code from the svn following the instructions at http://code.opencv.org . The compilation process worked fine for me for all the core modules + the Qt module + the GPU module + TBB acceleration.
The instructions are the same as the Linux platform.
After setting up cmake configuration in a terminal (using ccmake for a more interactive tool),
I set the architecture to x86_64 (on my MBP Core 2 Duo), the target directory to /usr/local/(the default), and I have Intel TBB installed in /usr/local/.
Cmake generates the makefiles for you, so you just have to type make -j2 to compile, then sudo make install. If you're working on a workstation, then you have more CPU power, and you can replace the value 2 by more, e.g. 8.

How to compile a Windows binary in Ubuntu?

I have a Qt application that I can compile in Ubuntu 10.04 64-bit and on Windows. However, I would like to avoid switching to Windows every time I want to compile the Windows version.
Is there a way I can compile a Windows Qt executable in Ubuntu with mingw32 or something?
Further, is there a way to integrate that compiler into Qt Creator?
There is a PPA (Personal Package Archive) for some people who are cross-compiling Qt and related software on Ubuntu for Windows. The PPA contains both the cross-compilers and the dependencies you will need to cross-compile Qt programs. If you look at the source packages there, I think you will be able to figure out how to configure your projects and build them.
If you most of your time spend coding with Qt on Linux (for example, Ubuntu), you may produce some experiment: install Wine, install Qt SDK for Windows with Wine and tried to build some simple project!
And if you don't like crazy things, which I wrote above, just use VirtualBox.

Resources