On Tue, Jul 7, 2015 at 2:25 PM, Steve Borho wrote:
> We're already adding -fPIC to the compile flags for the two object
> libraries. This way one set of objects can be used to output the shared
> library and the static library. So the C++ files are already compiled
> with -fPIC. It is only a probl
On 07/07, Dan Kegel wrote:
> On Tue, Jul 7, 2015 at 12:36 PM, Steve Borho wrote:
> > /bin/ld: common/CMakeFiles/common.dir/x86/pixel-a.asm.o: relocation
> > R_X86_64_PC32 against symbol `x265_pw_1' can not be used when making a
> > shared object; recompile with -fPIC
> > ...
> > 2 - is there some
On 07/07, Alexander Neundorf wrote:
> On Tuesday, July 07, 2015 14:36:25 Steve Borho wrote:
> > Hello, I am the technical lead for x265 (HEVC encoder) and we have used
> > cmake successfully since the beginning of the project. There are a few
> > rough edges that we've had to work around (uninstal
On Tue, Jul 7, 2015 at 12:36 PM, Steve Borho wrote:
> /bin/ld: common/CMakeFiles/common.dir/x86/pixel-a.asm.o: relocation
> R_X86_64_PC32 against symbol `x265_pw_1' can not be used when making a
> shared object; recompile with -fPIC
> ...
> 2 - is there some invocation that will force cmake to bui
On Tuesday, July 07, 2015 14:36:25 Steve Borho wrote:
> Hello, I am the technical lead for x265 (HEVC encoder) and we have used
> cmake successfully since the beginning of the project. There are a few
> rough edges that we've had to work around (uninstall rules, yasm support
> in MSVC, etc) but in
Hi,
I've been set up with OpenCV for about a month now (I'm using it on Mac and
on Android too), but I recently tried rebuilding OpenCV on both Mac and
Android and I haven't been able to due to multiple CMake errors.
Here's what I see when I try building:
cd opencv/platforms
rm -rf build_andro
Hello, I am the technical lead for x265 (HEVC encoder) and we have used
cmake successfully since the beginning of the project. There are a few
rough edges that we've had to work around (uninstall rules, yasm support
in MSVC, etc) but in general it has worked pretty well.
x265 can support a number
Dear all,
I came across a problem, for me it seems that cmake does not allow header
files to be have the same name. Or am I doing something wrong?
I have two projects, a library and an application. Both have files with
similar content, but the same file names. I am using cmake to compile the
app a
Hello!
I would like to download and compile a pair of C files (foo.h, foo.c) thanks to
the ExternalProject_Add function.
However, only one URL can be provided.
What is the cleanest way to handle such a case?
Cheers,
Cédric
--
Powered by www.kitware.com
Please keep messages on-topic