| Wrong include paths
Feb 9 2014 on content qNotesManager |
Your pro file contains the following lines (55-57):
INCLUDEPATH += src/qca/QtCrypto \
src/exceptions \
src/models
First there're no src/exceptions and src/models paths in your sources.
Second unconditional usage of your own copy of QCA headers creates conflicts with a system QCA library on non-Windows systems. Use your own copy of the headers only on Windows. On most Linux systems this path should be /usr/include/QtCrypto and thus using #include <QtCrypto/QtCrypto> in your source code you would completely eliminate the need to provide this path on 'unix' systems. |
|  | | Wrong library path in unix section of pro file
Feb 9 2014 on content qNotesManager |
Lines 60-61 in your pro contain wrong -L option with a wrong library search path.
First in contains a whitespace between -L and a path.
Second the path /usr/lib is a system path, it is used automatically and can vary on different systems and architectures (/usr/lib, /usr/lib32, /usr/lib64). Do not add it in LIBS. |
| | | Wrong path delimiter in qNotesManager.pro
Feb 9 2014 on content qNotesManager |
qmake gives me the following warning:
WARNING: /home/olelukoie/rpmbuild/BUILD/qNotesManager-0.9.4/qNotesManager.pro:8: Unescaped backslashes are deprecated.
This line #8 in the pro file states:
$(QTDIR)\include
It contains Windows-style path delimiter that won't work on non-windows systems and thus has to be changes. |
| | | Download link is wrong
Feb 9 2014 on content qNotesManager |
Your download link is called 'Source' but is redirected to Win32 binary version. Fix it please. |
| | | Re: Re: Error compiling
Oct 12 2009 on content PeaZip |
What do you mean with "you can replace"? How to do this? Do you provide an option that I've missed? I'm not a Pascal/Delphi/Lazarus developer so I need more exact instructions on what to do. |
| | | Error compiling
Oct 11 2009 on content PeaZip |
I have found the cause of the problem I've reported previously with compiling crc16.pas on x86_64. It is your std.inc file that has the following code:
{$ifndef BIT16}
{$define BIT32}
{$endif}
This is completely wrong for 64-bit system.
After I have removed these tree lines I have managed to go a bit farther and now I get the following build error:
Compiling md4.pas
md4.pas(354,7) Fatal: Syntax error, ";" expected but "(" found
I don't know how to fix this. It seems like the library you're using for crc/hashes processing is not 64-bit compatible at all and it worth to try to find something else. |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
