| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Due to a bug in the optimizer, the link hangs when building cogl-crate
on Visual Studio 2008 x64, and causes an internal compiler error when
linking cogl-msaa on pre-Visual Studio 2013 x64. Fix this by using /O1
instead of /O2 as needed on x64.
|
|
|
|
|
| |
They have been replaced by the NMake Makefiles, which will take over
their places in build/win32.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a set of NMake Makefiles that can be used to build Cogl on
Visual Studio 2008 or later, which will replace the former Visual Studio
2008/2010 project files. Improvements over the Visual Studio projects:
* Configurable by the flags that are passed into the NMake command
line, meaning that SDL/SDL2, Pango, Gst are enabled only if sepcified
on the NMake command line. Introspection is now also optionally
enabled for the libraries that are built. This will give us a more
flexible builds. Unit and conformance tests are also built
selectively as a result.
* Easier configuration for later Visual Studio versions.
* Will share the source listings that were split out from the autotools
build files, for easier maintenance--we will also be able to remove
the bits in the autotools build files that were used to generate the
Visual Studio project files. which will be in the next commit.
|
|
|
|
|
| |
This way, we can make the source listing shared with other non-autotools
Makefiles
|
|
|
|
|
| |
This is so that source listings can be shared with other non-autools
build systems, such as NMake.
|
|
|
|
|
| |
This is so that other non-autotools build systems can share the source
listings.
|
|
|
|
|
| |
This is done so that we can share the source listings with other
non-autotools build systems, such as NMake.
|
|
|
|
|
|
| |
Split out the source listings from cogl/Makefile.am, and make the base
sources more finely split, by the base sources, the deprecated sources
and common/stub winsys sources.
|
|
|
|
| |
Make things more uniform for easier maintenance.
|
|
|
|
|
|
|
|
|
| |
Some entries were added or changed in the generated config.h.in
template, so update config.h.win32.in to conform better to it.
Also, since we are shifting to a NMake-based build for Visual Studio,
just let NMake pass the compiler define flags for the optional features
that we might enable during the build.
|
|
|
|
|
|
| |
Visual Studio 2013+ has inttypes.h, and clean up some of the predefined
entries. Also, we have strncasecmp() via using _strnicmp() on Visual
Studio.
|
|
|
|
|
|
| |
This removes the need to maintain a separate file to export the symbols
on builds that do not support a regex-pattern export (such as Visual
Studio).
|
|
|
|
| |
It is no longer needed.
|
|
|
|
|
| |
This way, we no longer need to rely on cogl-pango.symbols to export
symbols, simplifying maintenance.
|
|
|
|
| |
It is no longer needed.
|
|
|
|
|
|
| |
This way we can use compiler directives to export public symbols, so
that we do not need to kepp cogl-path.symbols around anymore, reducing
maintenance efforts.
|
|
|
|
|
| |
This is intentionally kept to remind ourselves which calls in Cogl-Path
and Cogl-Pango we need to replace with Cogl's public symbols.
|
|
|
|
| |
This will ensure that the unit and conformance tests will build and run.
|
|
|
|
|
|
|
| |
This way we can use compiler directives to export public symbols instead
of relying on cogl.symbols which must be kept up-to-date. cogl.symbols
is still around to remind us of the calls for Cogl's private APIs in
Cogl-Path and Cogl-Pango that is still being used.
|
|
|
|
|
|
|
| |
This way we can reduce maintenance burden for the cogl.symbols file by
using compiler directives to export public symbols. cogl.symbols is
still now kept as we still need to get rid of the private API calls
within Cogl-Pango and Cogl-Path.
|
|
|
|
|
|
|
|
| |
This way we can reduce the maintenance burden for updating the
cogl.symbols files for the Visual Studio builds, as we can now export
symbols using __declspec(dllexport). The cogl.symbols file is still
kept to remind us of the usage of private Cogl symbols in Cogl-Path
and Cogl-Pango that we want to replace with public with public symbols.
|
|
|
|
|
|
| |
Things on Windows tend to be relocatable, so if cogl-crate failed to
find crate.jpg with the hard-coded path on Windows, try again using a
dynamically-constructed path.
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to also export the extern variables _cogl_debug_instances its
consumption in Cogl-Path, so that it can be properly referred to by
Cogl-Path and hence any other libraries that make use of them, such as
Clutter.
On Visual Studio DLL builds, this *must* also be marked with
__declspec(dllimport) when Cogl-Path is being built against Cogl so that
it can be referred to properly, otherwise one will be subject to crashes
as a result.
|
|
|
|
|
|
|
|
|
|
|
| |
CoglPollFD uses an int type for its fd member but the GPollFD that
g_poll() expects uses a gint64 type (a.k.a int64_t, __in64 on Windows)
for its fd member on 64-bit Windows, which will cause loads of
"WaitForMultipleObjectsEx failed:..." to be spewed from GLib on 64-bit
Windows.
This updates the example to use the correct types for the g_poll() call,
which will avoid this kind of situation.
|
|
|
|
|
|
|
| |
Using unsigned long is not safe as sizeof(long) is not necessary
sizeof(void*) on some platforms, such as Windows on Visual Studio. To
avoid this, use size_t instead of unsized long, and use the correct
unsigned suffix accordingly.
|
|
|
|
|
|
| |
Instead, we construct it according to where the Cogl DLL is found, as it
is likely that the Cogl DLL will land in somewhere that is not the
initial $(PREFIX)\bin on Windows.
|
|
|
|
|
|
| |
When we query for GL APIs, we need to ensure that we are using the
correct calling convention, otherwise running on 32-bit Windows will
crash.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
cogl-gles2: Fix undefined references.
See merge request GNOME/cogl!35
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Free state after freeing its contents
Closes #14
See merge request GNOME/cogl!25
|
|/
|
|
|
|
|
| |
We are freeing the big state inside the CoglPipeline before freeing the
snippets list, even though the snippets are stored in the big state.
Fixes: #14
|
|\
| |
| |
| |
| | |
Simple ci
See merge request GNOME/cogl!26
|
| |
| |
| |
| | |
Needs further experiments, as it completely fails on the CI runner.
|
| | |
|
| |
| |
| |
| |
| | |
Injecting this in the CPPFLAGS gets propagated into the introspection
build, which is not ideal, and will generate warnings.
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
cogl-xlib-renderer: Ensure we don't close the same X display twice
See merge request GNOME/cogl!23
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we don't do this, it results in a double-free that segfaults
test_atlas_migration on ES2, when running an x86_64 build under Xvfb
(probably other architectures and displays, I haven't checked).
==671783==ERROR: AddressSanitizer: SEGV on unknown address ...
==671783==The signal is caused by a READ memory access.
#0 0x7fbc0b5a28e7 in xcb_disconnect (...)
#1 0x7fbc0bfc2be8 in XCloseDisplay (...)
#2 0x7fbc0d6b8910 in _cogl_xlib_renderer_disconnect .../cogl/cogl-xlib-renderer.c:573
#3 0x7fbc0d6eba71 in _cogl_winsys_renderer_disconnect .../cogl/winsys/cogl-winsys-egl-x11.c:257
#4 0x7fbc0d6ebd7e in _cogl_winsys_renderer_connect .../cogl/winsys/cogl-winsys-egl-x11.c:289
#5 0x7fbc0d55e970 in cogl_renderer_connect .../cogl/cogl-renderer.c:687
#6 0x7fbc0d557dff in cogl_context_new .../cogl/cogl-context.c:202
#7 0x7fbc0d6fcce5 in test_utils_init .../test-fixtures/test-utils.c:176
#8 0x557c76a1c7f5 in main .../tests/conform/test-conform-main.c:90
#9 0x7fbc0c527bba in __libc_start_main ../csu/libc-start.c:308
#10 0x557c76a1b209 in _start (...)
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\
| |
| |
| |
| | |
[1.22] Terminate tests with SIGALRM if they take more than 120 seconds
See merge request GNOME/cogl!11
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Debian autobuilders run cogl's build-time tests to get an idea of
how much can be expected to work on each supported architecture.
We're currently ignoring test failures and running the tests for
information only, but if a test hangs, that will still cause the build
to fail (and tie up an autobuilder until a rather long timeout is
reached).
The fork of cogl in Mutter uses a 120 second timeout for tests in its
Meson build system, but other than that it's purely an arbitrary number.
dbus uses a similar alarm()-based watchdog, as do a couple of tests
in GLib.
Bug-Debian: https://bugs.debian.org/935592
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\ \
| | |
| | |
| | |
| | | |
[1.22] tests: Show the actual output from tests if VERBOSE is set
See merge request GNOME/cogl!14
|