A-men:

[100%] Built target freedv
david@penetrator:~/tmp/fdmdv2-dev/build_windows$ file src/freedv.exe
src/freedv.exe: PE32 executable (GUI) Intel 80386, for MS Windows

:-)

But will it run?

- David

On 17/06/15 06:03, David Rowe wrote:
> That's OK I have worked out how to do it, checked in the change to
> codec2-dev.
>
> Now lets see if that will let freedv2-dev build ......
>
> - David
>
> On 17/06/15 05:38, David Rowe wrote:
>> Hi Richard,
>>
>> I think we are rather close.  I am trying to build codec2-dev externally
>> to fdmdv2-dev. Can you pls tell me the correct syntax for driving
>> IMPORT_EXECUTABLES:
>>
>> ~/tmp/codec2-dev/build_windows$ cmake ..
>> -DCMAKE_TOOLCHAIN_FILE=../fdmdv2-dev/cmake/Toolchain-Ubuntu-mingw32.cmake 
>> -DUNITTEST=FALSE
>> -DIMPORT_EXECUTABLES=/home/david/codec2-dev/build_linux/
>> -- codec2 version: 0.3
>> -- Build type is: Release
>> -- Compiler Flags:  -Wall
>> -- System is MinGW.
>> -- Configuring done
>> -- Generating done
>> -- Build files have been written to:
>> /home/david/tmp/codec2-dev/build_windows
>> david@penetrator:~/tmp/codec2-dev/build_windows$ make
>> make[2]: *** No rule to make target `../src/generate_codebook', needed
>> by `src/codebookge.c'.  Stop.
>> make[1]: *** [src/CMakeFiles/codec2.dir/all] Error 2
>> make: *** [all] Error 2
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Freetel-codec2 mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Freetel-codec2 mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>

------------------------------------------------------------------------------
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to