Build automation for cef-binary

[jornh]

Over in the CefSharp repo - in cefsharp/CefSharp#288 (comment) @perlun suggested better automation. I think this belong in this repo - so here's an issue for it, with my comments so far ...

I started looking at creating a Rakefile for this, but it's not done yet. It might be that I won't have time for completing it until next week.

Hey, I thought you said with a Rakefile it would be a one-liner ... did you stop in the middle of the line ;-)

My idea is to provide vs2010, vs2012 and vs2013 targets, which will then launch the vsvars32.bat file for the proper VS version, and run msbuild. That way, you won't have to start up the right Developer Command Prompt; you can just make all of the targets at once using one single Rake command.

Brilliant thought - I have actually started the same - but in BAT ... eek ... based on https://github.com/coapp-packages/pixman/blob/master/COPKG/build.bat

I know you might not be a big Ruby fan (yet ) but I feel it will be very convenient that way. Yes, people might have to do cinst ruby but that's something that they should be doing anyway... Besides, the number of people hacking on cef-binary is very low anyway so a slightly higher requirement in terms of tooling is quite OK as far as I'm concerned. (AFAIC?)

I'll see if I can get to it before you. cinst'ing (should be a word!) FTW

[perlun]

Hey, I thought you said with a Rakefile it would be a one-liner ... did you stop in the middle of the line 😉

No comments... 😄

I'll see if I can get to it before you.

Be my guest! Here is my attempt so far. As you see, I didn't get very far. 😉 The hard bit is about chaining the vsvars32.bat call with the msbuild call; they need to run inside the same cmd.exe instance (since the VS vars & path settings must persist to msbuild). If you can get that working, the rest should be quite simple:

desc 'Compile using VS2010, VS2012 and VS2013. Note that this requires all toolchains to be installed and available.'
task :default => [ :vs2012 ]

# TODO: implement
#desc 'Compile using VS2010 tools'
#task :vs2010 do
#end

desc 'Compile using VS2012 tools'
task :vs2012 do
  sh 'cmd /c C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\vsvars32.bat'
end

# TODO: implement
#desc 'Compile using VS2013 tools'
#task :vs2013 do
#end

cinst'ing (should be a word!) FTW

It is a word. You just created it. 😀

[perlun]

Btw, I already added the Rakefile into the repo if you didn't already see it.

[jornh]

Yes, saw it. Good start and the &&'s are a neat solution to the chaining problem. 👍

Still first I think I will spend a little time on tightening things up on native NuGets etc. & follow up with FAQ etc. when people start using them ...

[perlun]

Yes, saw it. Good start and the &&'s are a neat solution to the chaining problem.

Thanks. I didn't know about && on Windows myself, but apparently, it's there...

Still first I think I will spend a little time on tightening things up on native NuGets etc. & follow up with FAQ etc. when people start using them ...

I see. My reference to FAQ was more so we can avoid the (obvious) question of "why can I not just clone the CefSharp code and build" (since the package restore needs to be done manually).

[jornh]

Yes - both the obvious one you mention and probably other variants that will crop up. There recently was some "FUD"/confusion in the Google group regarding NuGet references etc. And I think I actually might have added to it with my comment there. 😢 needs to be straightened out ...

[jornh]

With the excellent build.ps1 from #11 this is resolved. Only downside is there's no .rb in it 😆 we'll simply have to live with that.