cerbero and Visual Studio/MSVC (under Windows 64 bit, for Windows 64 bit)

[Martin Maurer]

Hello Nirbheek,

I am doing some progress. I meanwhile was able to build the x86_64 
(win64) release with meson-1.10.

The missing command was the "wipe" (to clean build directory).

Now afterwards I directly tried the x86 (win32) build in same 
directories. But again got compile errors.

Now executed the wipe again and trying the win32 build (still running, 
reached already 18 from 80)

I have my files on e: and starting the build there.

When calling the wipe for win32 I see the following:

$ /c/Python27/python2.exe ./cerbero-uninstalled -c 
config/win32-mixed-msvc.cbc wipe
WARNING!!!
This command will delete cerbero's build cache, the sources directory, 
and the builds directory to reset the build system to its initial state.
The following paths will be removed:
e:/gstreamer-cerbero-meson-1.10/build/windows_x86.cache
c:/gstreamer/1.0/x86_64

*** Here it is using x86_64 instead of x86? Is it correct? What does it 
do out-of-build-tree on c:\?

*** Could this location be influences somehow to move it also to 
somewhere under e:/gstreamer-cerbero-meson-1.10?

*** Finally our build server does support out-of-tree-content outside 
the working directory. Any idea?

*** Where is this location defined? Single or multiple places?

e:/gstreamer-cerbero-meson-1.10/build/logs/windows_x86
e:/gstreamer-cerbero-meson-1.10/build/sources/windows_x86
Do you want to continue? [yes/no] yes
Are you sure? [yes/no] yes
-----> Removing path: 
e:/gstreamer-cerbero-meson-1.10/build/windows_x86.cache
-----> Removing path: c:/gstreamer/1.0/x86_64
-----> Removing path: e:/gstreamer-cerbero-meson-1.10/build/logs/windows_x86
-----> Removing path: 
e:/gstreamer-cerbero-meson-1.10/build/sources/windows_x86

Just for my understanding:

A full build (the ~80 steps...) without meson takes a long time 
(multiple hours).

Do you have a comparison, how long it does take with/without meson,

on same machine, with same sources/version?

Only a few packages can be built with MSVC, so the others still take hours?

Or is time saving only available when doing a partial build for a single 
package,

like during debugging/fixing some problem,

but no real great advantage when only building complete package?

And of course the big advantage to be able to debug with Visual Studio 
IDE, use breakpoints and so on.

Many thanks!

Best regards,

Martin


Am 24.04.2017 um 12:07 schrieb Nirbheek Chauhan:
> On Sun, Apr 23, 2017 at 11:52 PM, Martin Maurer
> <meinemailingliste2 at online.de> wrote:
>> many thanks for your answer. How big is such an action?
>> Just copying a few file or endless merging? Just to get a feeling...
>> Do you think it still could be inside official release of 1.12
>> to save you effort to merge it again and again?
>> Or is it already too late for such an action?
>> Is "time" the only blocking point, or still other things which must be
>> clarified
>> before it can go into an official release?
>>
> It's just a matter of getting the time to do it. It won't be in the
> 1.12 upstream release, but I hope to get it ready for the next one.
>
>> I meanwhile went back to branch meson-1.10 and use this for initial
>> (learning) steps.
>> When 1.12 is ready for meson I can move to the new version.
>>
>> I have an additional question:
>>
>> Do I need to call
>>
>>> cerbero-uninstalled -c config/win64-mixed-msvc.cbc bootstrap
>> before something else (in every case)
>>
> Bootstrap only needs to be called once. You may need to call it again
> after updating Cerbero itself.
>
>> or can I directly call
>>
>>> cerbero-uninstalled -c config/win64-mixed-msvc.cbc package gstreamer-1.0
>> (because it is doing the bootstrap automatically here)?
>>
> No command will automatically run bootstrap for you.
>
>> When building e.g. a 64 bit and a 32 version, do I need some kind of a
>> clean?
>> Or would a clean be even a bad thing, because in second build some steps can
>> be skipped,
>> because it was already built in first build?
>>
> 64-bit and 32-bit versions are completely independent. They build
> inside separate subdirs of the cerbero build directory.
>
>> The meson 1.10 reports some errors. Are you interested to collect such
>> errors?
>> Here via email? Or in the bug-tracker?
>>
> I looked at the log in your email. The main issue seems to be that you
> did not run a `clean` command when you switched branches to
> meson-1.10. Please do that so that stale files built by the previous
> Cerbero branch you were using are removed.
>
> I was recently told by someone that they ran it all from scratch and
> built both 32-bit and 64-bit successfully, and also used it in their
> application, so it should work.
>
> Cheers,
> Nirbheek
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel