| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
variable DISABLE_AESNI to 1 during build or passing NOAESNI=1 to make command
This comes following Github issue #892 and which should be solved thanks to this.
|
|
* *: source files should not be executable
* *: make sure files have final newline
* *: remove BOM from text files
* translations: unify headers
* *: fix typos
* *: trim excess whitespace
|
|
default. (#815)
This tries to figure out, via wx-config, if you're using GTK2 or GTK3
and uses the associated Ayatana library.
|
|
|
|
This fixes compilation issues when using GNU GCC >=11 where parameter -std=gnu++17 is used by default. Resolves #802
|
|
* OpenBSD: add basic support
modified: Build/Include/Makefile.inc
modified: Driver/Fuse/FuseService.cpp
modified: Main/FatalErrorHandler.cpp
modified: Makefile
modified: Platform/Unix/File.cpp
modified: Platform/Unix/FilesystemPath.cpp
modified: Platform/Unix/SystemInfo.cpp
* OpenBSD: some necessary files were missing
new file: Core/Unix/OpenBSD/CoreOpenBSD.cpp
new file: Core/Unix/OpenBSD/CoreOpenBSD.h
new file: Core/Unix/OpenBSD/System.h
|
|
* Added Translations/Language.he.xml
* translate
* changes
* changes
* changes
* changes
* changes
* changes
* changes
* fixed RTL points
* changes
* Removed hebrew string vowels
* changes
* Changed Makefile path
* changes
* changes
* fixed strings with variables
|
|
The Makefile should respect the value of CC even when performing
build-related tests.
Bug: https://bugs.gentoo.org/756787
|
|
|
|
* Revert "Linux: Fix failure to run VeraCrypt binary built for console mode on headless machines (fix issue https://github.com/veracrypt/VeraCrypt/issues/531)"
The build failure still exists for system wxGTK compiled with '--disable-gui':
```
In file included from TextUserInterface.cpp:27:
TextUserInterface.h: In member function ‘virtual bool VeraCrypt::TextUserInterface::Initialize(int&, wxChar**)’:
TextUserInterface.h:50:63: error: ‘wxAppBase’ has not been declared
50 | virtual bool Initialize (int &argc, wxChar **argv) { return wxAppBase::Initialize(argc, argv); }
```
This reverts commit 737e1f126b8826ed02418266e590e195aebdd7c0.
* Revert "Linux: fix compilation error when building console-only version of VeraCrypt that is statically linked to wxWidgets"
The build failure still exists for system wxGTK compiled with '--disable-gui':
```
In file included from TextUserInterface.cpp:27:
TextUserInterface.h: In member function ‘virtual bool VeraCrypt::TextUserInterface::Initialize(int&, wxChar**)’:
TextUserInterface.h:50:63: error: ‘wxAppBase’ has not been declared
50 | virtual bool Initialize (int &argc, wxChar **argv) { return wxAppBase::Initialize(argc, argv); }
```
This reverts commit 14bee5e6a227701e78c5fec04064c0494f6361f0.
* src/Main/Main.make: simplify the WX_CONFIG_LIBS logic
Irrespective of whether we are linking against widgets statically or
dynamically, pull in only 'base' when GUI is disabled, and
'adv,core,base' when GUI is enabled. When GUI is disabled, the C/CXX
flag must include '-DwxUSE_GUI=0' for this to work.
* src/Makefile: pass '-DwxUSE_GUI=0' when NOGUI=1
veracrypt with NOGUI=1 fails to properly link against wxGTK compiled
with '--disable-gui' only using the 'base' library because the wx's
setup.h implicitly defines wxUSE_GUI=1, which then changes the
definition of various structures, requiring symbols from the core
library as well.
For example, wxwidgets include/wx/app.h defines:
#if wxUSE_GUI
class WXDLLIMPEXP_CORE wxAppBase : public wxAppConsole
...
[snip]
...
#else // !GUI
// wxApp is defined in core and we cannot define another one in wxBase,
// so use the preprocessor to allow using wxApp in console programs too
#define wxApp wxAppConsole
#endif // GUI/!GUI
To fix this, pass '-DwxUSE_GUI=0' when compiling veracrypt with
NOGUI=1.
Closes: https://github.com/veracrypt/VeraCrypt/issues/531
|
|
that is statically linked to wxWidgets
|
|
Signed-off-by: alt3r 3go <alt3r.3go@protonmail.com>
|
|
Added new variable 'VC_OSX_SDK' to differentiate between the OSX minimum target and the SDK to use for building.
|
|
3.1.2 for non legacy build targeting OSX 10.9+
|
|
|
|
This can be useful when crossbuilding or building in a chroot where using
uname -m would cause the wrong compiler options.
|
|
don't support SSE2 instructions.
|
|
This patch was provided by Krytarik Raido via unit93
https://github.com/veracrypt/VeraCrypt/issues/198#issuecomment-341453420
|
|
|
|
|
|
code of SHA-512 since it is not compatible with PIE configuration of OSX compiler (absolute addressing used)
|
|
|
|
|
|
install target for local installation.
|
|
Randomization (ASLR).
|
|
|
|
compiler doesn't support GAS syntax
|
|
Slackware build issue.
|
|
|
|
x64 (for example ARM).
|
|
compiler
|
|
code to gcc.
|
|
|
|
Veracrypt for build under GCC6 required using compatibility flag `-std=c++98` against change default C++ frontend in GCC6.
The C++ frontend now defaults to C++14 standard instead of C++98 it has
been defaulting to previously, for compiling older C++ code that might
require either explicitly compiling with selected older C++ standards,
or might require some code adjustment, see
http://gcc.gnu.org/gcc-6/porting_to.html for details. The experimental
C++17 support has been enhanced in this release.
from: https://gcc.gnu.org/ml/gcc-announce/2016/msg00000.html
|
|
|
|
building using gcc-5 by disabling the new C++ ABI. For this to work, wxWidgets static library must be built and used by VeraCrypt by specifying WXSTATIC=1 in make command line.
|
|
|
|
and TrueCrypt 3.0.
|
|
especially under Ubuntu.
|
|
|
|
mode. Modify Makefiles to correct compilation process using latest Xcode.
|
|
helper scripts. The original TrueCrypt sources didn't contain anything about this.
|
|
3.0 and remove unneeded dependencies to ensure maximum compatibility.
|
|
|
|
specified elsewhere.
|
|
|
|
|
