Is it possible to add styles for PySide2, Currently i just have "fusion", "windows", "windowsvista". I wanted to fetch more styles.
I followed steps from 63477276 and 39201227.
After looking into those questions, there are actually more than just 3 predefined styles in qt but we need to manually fetch them, i was trying to fetch those
cd src\ && ( if not exist Makefile C:\mingw\bin\qmake.exe Tests\qtstyleplugins\src\src.pro -o Makefile ) && C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -f Makefile
make[1]: Entering directory 'Tests/qtstyleplugins/src'
cd plugins\ && ( if not exist Makefile C:\mingw\bin\qmake.exe Tests\qtstyleplugins\src\plugins\plugins.pro -o Makefile ) && C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -f Makefile
make[2]: Entering directory 'Tests/qtstyleplugins/src/plugins'
cd platformthemes\ && ( if not exist Makefile C:\mingw\bin\qmake.exe Tests\qtstyleplugins\src\plugins\platformthemes\platformthemes.pro -o Makefile ) && C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -f Makefile
make[3]: Entering directory 'Tests/qtstyleplugins/src/plugins/platformthemes'
make[3]: Nothing to be done for 'first'.
make[3]: Leaving directory 'Tests/qtstyleplugins/src/plugins/platformthemes'
cd styles\ && ( if not exist Makefile C:\mingw\bin\qmake.exe Tests\qtstyleplugins\src\plugins\styles\styles.pro -o Makefile ) && C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -f Makefile
make[3]: Entering directory 'Tests/qtstyleplugins/src/plugins/styles'
cd cleanlooks\ && ( if not exist Makefile C:\mingw\bin\qmake.exe Tests\qtstyleplugins\src\plugins\styles\cleanlooks\cleanlooks.pro -o Makefile ) && C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -f Makefile
Project ERROR: No module claims plugin type 'styles'
make[3]: *** [Makefile:41: sub-cleanlooks-make_first] Error 3
make[3]: Leaving directory 'Tests/qtstyleplugins/src/plugins/styles'
make[2]: *** [Makefile:65: sub-styles-make_first] Error 2
make[2]: Leaving directory 'Tests/qtstyleplugins/src/plugins'
make[1]: *** [Makefile:39: sub-plugins-make_first] Error 2
make[1]: Leaving directory 'Tests/qtstyleplugins/src'
make: *** [Makefile:39: sub-src-make_first] Error 2
With that step, i was not able to convert .cpp to .dll files (for windows)
version: 5.15.2
os: windows
before that step, i cloned repo from code.qt
Is there any other way to add styles for pyside2.
Related
I am trying to install emacs ESS using GNU make.
i follow the installation instructions for ESS found in the following
link:
steps 2 and 3 :
http://ess.r-project.org/Manual/ess.html#Installation
for each step i get errors when using make:
below are the instructions and the error messages for each step:
First Instruction:
Optionally, compile elisp files and build the documentation with:
cd /path/to/ESS/
make
Without this step, info, pdf and html documentation and reference card will not be available.
My Action:
C:\Program Files\ESS\ess-17.11>make
System Messages:
cd etc; make all
make[1]: Entering directory `/cygdrive/c/Program Files/ESS/ess-17.11/etc'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/cygdrive/c/Program Files/ESS/ess-17.11/etc'
cd lisp; make all
make[1]: Entering directory `/cygdrive/c/Program Files/ESS/ess-17.11/lisp'
emacs -batch -no-site-file -no-init-file -l ./ess-comp.el -f batch-byte-compile ess-custom.el
emacs: not found
make[1]: [ess-custom.elc] Error 127
make[1]: Leaving directory `/cygdrive/c/Program Files/ESS/ess-17.11/lisp'
make: [all] Error 2
Second Instruction:
Optionally, install into your local machine with make install. You might need administrative privileges:
make install
The files are installed into /usr/share/emacs directory. For this step to run correctly on macOS, you will need to adjust the PREFIX path in Makeconf. The necessary code and instructions are commented in that file.
My Action:
C:\Program Files\ESS\ess-17.11>make install
System Messages:
cd etc; make install
make[1]: Entering directory `/cygdrive/c/Program Files/ESS/ess-17.11/etc'
mkdir -p /usr/share/emacs/etc/ess/icons
mkdir -p /usr/share/emacs/etc/ess/ESSR/R
cp -p .IS.RELEASE git-ref *.S sas-keys.* ess-sas-sh-command *.jl /usr/share/emacs/etc/ess
cp -p icons/*.xpm /usr/share/emacs/etc/ess/icons
cp -p ESSR/LOADREMOTE ESSR/VERSION /usr/share/emacs/etc/ess/ESSR
cp -p ESSR/R/*.R ESSR/R/.*.R /usr/share/emacs/etc/ess/ESSR/R
chmod +x /usr/share/emacs/etc/ess/ess-sas-sh-command
chmod: not found
make[1]: *** [install] Error 127
make[1]: Leaving directory `/cygdrive/c/Program Files/ESS/ess-17.11/etc'
make: *** [install] Error 2
I'll appreciate you help with installing ESS using make.
Thanks
Rafael
You are trying to execute under Windows commands, which are for Linux environments.
Specifically, your installation fails at the following lines:
emacs -batch -no-site-file -no-init-file -l ./ess-comp.el -f batch-byte-compile ess-custom.el
emacs: not found
and
chmod +x /usr/share/emacs/etc/ess/ess-sas-sh-command
chmod: not found
There is no chmod command under Windows. Here is the cmd equivalent: https://www.cyberciti.biz/tips/windows-change-access-permissions-from-the-command-line.html
The ESS Manual you provided suggests the following approach:
Note for Windows and macOS users: The most straightforward way to
install Emacs on your machine is by downloading the Emacs binary by
Vincent Goulet; either Emacs Modified for macOS or from Emacs Modified
for Windows.
I also suggest that you install the Emacs Modified for Windows, as installation via make under windows will be too difficult/costly - virtually impossible.
I have a makefile
jumbo: objs/jumbo.o objs/utils.o
objs/%.o: %.C
$(CXX) $(CFLAGS) $(CPPFLAGS) -c -o $# $<
The result of the compile
g++ jumbo.C objs/jumbo.o objs/utils.o -o jumbo
objs/jumbo.o:jumbo.C:(.text+0x0): multiple definition of `main'
/tmp/ccwEFt9o.o:jumbo.C:(.text+0x0): first defined here
collect2: error: ld returned 1 exit status
make: *** [<builtin>: server] Error 1
if I replace the definition of jumbo
jumbo: jumbo.C objs/utils.o
the problem goes away but the object file is not put away in the objs directory
And I don't know whether it is recompiling jumbo or not when it should only be relinking
You haven't defined any recipe for building the target jumbo. Because of that, make looks for a built-in rule and there is one that knows how to build a file X from a file X.C. Make looks at the directory and lo and behold, there's an X.C (jumbo.C) that exists, so make chooses to use that built-in rule. The built-in rule is:
%: %.C
$(LINK.C) $^ $(LOADLIBES) $(LDLIBS) -o $#
so, since jumbo depends on objs/jumbo. and objs/utils.o directory plus the jumbo.C from the default implicit rule, you get all three on the command line.
To fix this just define your own recipe for creating jumbo:
jumbo: objs/jumbo.o objs/utils.o
$(LINK.C) $^ $(LOADLIBES) $(LDLIBS) -o $#
While installing openldap, I am getting below error and compilation stops, please advice.
cc -g -I../../../include -I../../../include -I.. -I./.. -I./../../../libraries/liblmdb -I/sites/bdb/include -c ./../../../libraries/liblmdb/mdb.c -o mdb.o
"./../../../libraries/liblmdb/mdb.c", line 4625: warning: implicit function declaration: pthread_mutexattr_setrobust
"./../../../libraries/liblmdb/mdb.c", line 4625: undefined symbol: PTHREAD_MUTEX_ROBUST
"./../../../libraries/liblmdb/mdb.c", line 10002: warning: implicit function declaration: pthread_mutex_consistent
cc: acomp failed for ./../../../libraries/liblmdb/mdb.c
Makefile:309: recipe for target 'mdb.lo' failed
gmake[3]: *** [mdb.lo] Error 1
gmake[3]: Leaving directory '/sites/openldap-2.4.44/servers/slapd/back-mdb'
Makefile:541: recipe for target '.backend' failed
gmake[2]: *** [.backend] Error 1
gmake[2]: Leaving directory '/sites/openldap-2.4.44/servers/slapd'
Makefile:291: recipe for target 'all-common' failed
gmake[1]: *** [all-common] Error 1
gmake[1]: Leaving directory '/sites/openldap-2.4.44/servers'
Makefile:312: recipe for target 'all-common' failed
gmake: *** [all-common] Error 1
[/sites/openldap-2.4.44]
I have configured bdb as below:
cd /sites/db-4.8.30/build_unix/
../dist/configure --prefix=/sites/bdb
make
make install
Installing openldap:
cd openldap-2.4.44/
./configure --prefix=/sites/openldap --enable-dynamic --enable-spasswd --enable-slapd --enable-mdb --enable-monitor
make depend
make all
I am getting above error at last step.
Below is the env
atg#lynntools01$ uname -a
SunOS lynntools01 5.10 Generic_150400-30 sun4v sparc sun4v
I am trying to compile the quazip source, under wdinwso 7 with QT5.4.
I tried compiling unders VS 2013, but the rc.exe file is not found. I made sure that the rc.exe and dll were in the kits and SDK folders for both vs2013 and vs2010.
So I followed this: http://www.maefloresta.com/portal/quazip
When i do so, I get the following error message, and am not sure where to start looking.
C:\development\QTCommon\quazip>mingw32-make
cd quazip\ && ( if not exist Makefile C:\development\QT\5.4\5.4\msvc2013_64\bin\
qmake.exe C:\development\QTCommon\quazip\quazip\quazip.pro -o Makefile ) && ming
w32-make -f Makefile
mingw32-make[1]: Entering directory 'C:/development/QTCommon/quazip/quazip'
mingw32-make -f Makefile.Release
mingw32-make[2]: Entering directory 'C:/development/QTCommon/quazip/quazip'
cl -c -nologo -Zm200 -Zc:wchar_t -FS -O2 -MD -Zc:strictStrings -W3 -w34100 -w341
89 -GR -EHsc -DUNICODE -DWIN32 -DQUAZIP_BUILD -DNOMINMAX -DQT_NO_DEBUG -DQT_CORE
_LIB -DNDEBUG -I"." -I"C:\development\QT\5.4\5.4\msvc2013_64\Src\qtbase\src\3rdp
arty\zlib" -I"C:\development\QT\5.4\5.4\msvc2013_64\include" -I"C:\development\Q
T\5.4\5.4\msvc2013_64\include\QtCore" -I"release" -I"C:\development\QT\5.4\5.4\m
svc2013_64\mkspecs\win32-msvc2013" -Forelease\ #<<
<< was unexpected at this time.
Makefile.Release:116: recipe for target '{release}.cpp{release\}.obj' failed
mingw32-make[2]: *** [{release}.cpp{release\}.obj] Error 255
mingw32-make[2]: Leaving directory 'C:/development/QTCommon/quazip/quazip'
Makefile:34: recipe for target 'release' failed
mingw32-make[1]: *** [release] Error 2
mingw32-make[1]: Leaving directory 'C:/development/QTCommon/quazip/quazip'
Makefile:41: recipe for target 'sub-quazip-make_first' failed
mingw32-make: *** [sub-quazip-make_first] Error 2
The makefile.release line found from quazip:
####### Implicit rules
.SUFFIXES: .c .cpp .cc .cxx
{release}.cpp{release\}.obj::
$(CXX) -c $(CXXFLAGS) $(INCPATH) -Forelease\ #<<
$<
<<
Any help would be great, for either the make or the vs 2013 issues.
Cheers.
If you are following the instructions from the link provided (http://www.maefloresta.com/portal/quazip) probably the origin of the problem could come because you are not build properly the QuaZIP libraries or because your include path or library path are wrong.
If you want a full example that works perfectly about how to use QuaZIP in Qt, I recommend you to check this entry of my blog: http://www.antonioborondo.com/2014/10/22/zipping-and-unzipping-files-with-qt/
My setup as below
# export PATH=/usr/sbin:/usr/bin:/usr/local/bin:/usr/sfw/bin:/usr/ccs/bin
# ./configure --prefix=/usr/local/nginx --user=webservd --group=webservd --with-http_stub_status_module --with-openssl=/usr/local/ssl/bin/openssl --with-debug --with-pcre=/usr/local/bin
and i get error code as such when i execute make
# make
make -f objs/Makefile
make[1]: Entering directory `/export/home/myhome/nginx-0.7.63'
cd /usr/local/bin \
&& if [ -f Makefile ]; then make distclean; fi \
&& CC="gcc" CFLAGS="-O2 -fomit-frame-pointer -pipe " \
./configure --disable-shared
/bin/sh: ./configure: not found
make[1]: *** [/usr/local/bin/Makefile] Error 1
make[1]: Leaving directory `/export/home/myhome/nginx-0.7.63'
make: *** [build] Error 2
any idea how to fix it?
That initial cd to /usr/local/bin looks very strange; are you building it in the global /usr tree?
It looks as if it's cd:ing to the wrong directory, for some reason. Look in the referenced Makefile (objs/Makefile) and try to figure out why.
UPDATE: It seems the problem is that it's trying to build the PCRE library. If you have it pre-built, that seems like an odd decision. This blog post suggests using the --with-cc-opt="-I /usr/include/pcre" option to point out to the configure script where you have headers for PCRE, might be worth trying.