Transform360 issues building for Windows
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cmake, cpp
- Domain
- build-system, computer-graphics
Research direction
Start with libavfilter/vf_transform360.c, especially generate_map and the VideoFrameTransform_new reference, then inspect how the VS2015-built Transform360.lib is produced and passed through the configure command. Reproduce the Windows MSYS2 build and determine whether the library and FFmpeg toolchains are link-compatible; done means make completes without the undefined-reference error.
Written by the indexing model from the issue text.
Description
Hi,
As others seem to have had, I am getting issues building ffmpeg with Transform360. I am using MSYS2 and the CMake produces a VisualStudio2015 solution to build a Transform360.lib. I then use this via the configure command...
./configure --prefix=ffmpeg/ --extra-cflags=-I"/usr/local/include" --extra-ldflags='-L/usr/local/lib -static' --pkg-config-flags="--static" --enable-nonfree --enable-gpl --enable-static --disable-shared --enable-libx264 --enable-libx265 --enable-libfdk_aac --enable-nvenc --extra-libs='Transform360.lib'
The subsequent 'make' call then spits out the error...
libavfilter\libavfilter.a(vf_transform360.o): In function generate_map':
C:\msys64\home\stebu\ffmpeg_nvidia_cubemap2/libavfilter/vf_transform360.c:140: undefined reference to VideoFrameTransform_new'
C:\msys64\home\stebu\ffmpeg_nvidia_cubemap2/libavfilter/vf_transform360.c:140:(.text+0x57f): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `VideoFrameTransform_new'
I am betting it is because the transform lib has been made with VS compiler, and ffmpeg is being compiled with gcc...
Can anyone offer any guidance?
Thanks!
- Dominant language
- C++
- Stars
- 1k
- Forks
- 242
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from facebook/transform360
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
facebook/transform360#76 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
facebook/transform360#74 ·
-
gcc questionOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
facebook/transform360#73 · 2 comments ·
-
License conflictOpen
Difficulty 1/5 Under an hour Newbie friendliness 38/100
facebook/transform360#71 ·
-
Windows buildOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
facebook/transform360#69 · 13 comments ·
All issues in facebook/transform360
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
shadps4-emu/shadps4-qtlauncher#453 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
plengauer/DXGIOutputDuplication#76 ·
Maintainers usually reply within 1 day
-
Feature
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Narezzurri/OpenVPN-Config-Manager#95 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rhalbersma/xstd-bits#314 ·
Maintainers usually reply within 1 day