use fsianycpu.exe instead of fsi.exe.

[tkesselring]

We would like to use Fake also as a 64 bit application.

[forki]

we tried 64bit, but it breaks so many existing build scripts because of registry, COM and many other fuckups. But maybe we can create a second nuget package.

[tkesselring]

Shall we prepare a nuget Package, or will you do this?

Tobias

On 03.11.2014, at 16:57, Steffen Forkmann notifications@github.com wrote:

we tried 64bit, but it breaks so many existing build scripts because of registry, COM and many other fuckups. But maybe we can create a second nuget package.

—
Reply to this email directly or view it on GitHub.

[forki]

I always wanted to do this, but didn't find the time.
So if you really need it, then it would probably help if you try to modify FAKE's build process to create a second package. ;-)

[forki]

I think we should fall back if the fsianycpu can't be found

[tkesselring]

As fsi.exe lies at the same place as fsianycpu.exe, what would be the fall back? On the other hand just using the old line containing "fsi.exe" would be fine because of the same reason.

[forki]

No this one is actually a separate process. But it's not used in the normal
FAKE process.
On Nov 4, 2014 10:39 AM, "tkesselring" notifications@github.com wrote:

In src/app/FakeLib/FSIHelper.fs:

     if fi.Exists then fi.FullName else

•    findPath "FSIPath" FSIPath "fsi.exe"
  

•    findPath "FSIPath" FSIPath "fsianycpu.exe"
  

As fsi.exe lies at the same place as fsianycpu.exe, what would be the fall
back? On the other hand just using the old line containing "fsi.exe" would
be fine because of the same reason.

—
Reply to this email directly or view it on GitHub
https://github.com/fsharp/FAKE/pull/582/files#r19792615.

[tkesselring]

At the end it seems, only the change of the bitness of the Fake-Project had impact.

[tkesselring]

I modified the build script s.t. it creates a second nuget package which is any cpu.
I can not run the full release process, therefore can you test it?

[forki]

nice. will try in ca. 2 days since im out of office.

[forki]

this looks cool. Is it ready to merge?

[tkesselring]

I think yes, it worked for me locally.

[forki]

I think this could be helpful in a separate FAKE helper

[forki]

ok we're generating way to many x64 packages.
I think only FAKE, Fake.Core and FAKE.Deploy should be x64tified

[forki]

it's released with 3.9. - can you verify that it works?

[tkesselring]

"ok we're generating way to many x64 packages.
I think only FAKE, Fake.Core and FAKE.Deploy should be x64tified"
As far as I understand it the other packages depend on Fake and Fake.Core, hence two sets are needed for all of them.

[tkesselring]

I checked it out. Works wonderful for my Project. thx.

[forki]

packages depend on Fake and Fake.Core

good point

[forki]

3.9 release is out and everything seems to work fine. Thanks

[forki]

ok. we did it wrong.
Now the normal FAKE is anyCPU and breaks all our builds.

[forki]

now it works for us again. But I assume I broke yours. So what should we do?

[tkesselring]

I think I made the 32bit-version anycpu and the 64bit-version 32-bit.
I just fixed this on my github account. But I need to test it first.