CosmosOS / Cosmos

Cosmos is an operating system "construction kit". Build your own OS using managed languages such as C#, VB.NET, and more!
https://www.goCosmos.org
BSD 3-Clause "New" or "Revised" License
2.93k stars 553 forks source link

Error Running Setup #471

Closed mmcc1 closed 8 years ago

mmcc1 commented 8 years ago

I have downloaded the latest repo and have all the prerequisites installed. Everything seems to go well with the build, but upon running as it moves to the 'Running Setup' stage, it throws an error. Below is the output. I've only kept the relevant portions:

Checking Prerequisites

Note: This check only prerequisites for building, please see website for full list. Checking for x86 run. Checking Operating System Check if User Kit Installer is already running. Checking if Visual Studio is running. Checking if Builder is already running. Checking for Visual Studio 2015 Checking for Microsoft Visual Studio 2015 SDK - ENU Checking for .NET 3.5 SP1 Checking for .NET 4.03 Checking for Inno Setup Checking for Inno Preprocessor Checking for VMware Workstation Checking for VMware Player

Cleaning up VSIP Folder

Deleting build output directory. C:\Dev\Cosmos-master\Build\VSIP

Compiling Cosmos

Starting: C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe Params: /t:Clean "C:\Dev\Cosmos-master\source\Build.sln" /nologo /maxcpucount /p:Configuration="Debug" /p:Platform="Any CPU" /p:OutputPath="C:\Dev\Cosmos-master\Build\VSIP" Build started 18/09/2016 00:00:11. 1>Project "C:\Dev\Cosmos-master\source\Build.sln" on node 1 (Clean target(s)). 1>ValidateSolutionConfiguration: Building solution configuration "Debug|Any CPU". 1>Project "C:\Dev\Cosmos-master\source\Build.sln" (1) is building "C:\Dev\Cosmos-master\source\Cosmos.Core.Memory\Cosmos.Core.Memory.csproj" (2) on node 1 (Clean target(s)). 2>Project "C:\Dev\Cosmos-master\source\Cosmos.Core.Memory\Cosmos.Core.Memory.csproj" (2) is building "C:\Dev\Cosmos-master\source\Cosmos.Common\Cosmos.Common.csproj" (3) on node 1 (Clean target(s)).

Time Elapsed 00:00:00.76

Starting: C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe Params: /t:Build "C:\Dev\Cosmos-master\source\Build.sln" /nologo /maxcpucount /p:Configuration="Debug" /p:Platform="Any CPU" /p:OutputPath="C:\Dev\Cosmos-master\Build\VSIP" Build started 18/09/2016 00:00:12. 1>Project "C:\Dev\Cosmos-master\source\Build.sln" on node 1 (Build target(s)).

 1>Project "C:\Dev\Cosmos-master\source\Build.sln" (1) is building "C:\Dev\Cosmos-master\source\Cosmos.Debug.Common\Cosmos.Debug.Common.csproj" (3) on node 3 (default targets).
 3>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "System.Data.SQLite, Version=1.0.99.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. [C:\Dev\Cosmos-master\source\Cosmos.Debug.Common\Cosmos.Debug.Common.csproj]

 1>Project "C:\Dev\Cosmos-master\source\Build.sln" (1) is building "C:\Dev\Cosmos-master\source\Cosmos.VS.Windows\Cosmos.VS.Windows.csproj" (24) on node 4 (default targets).
24>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed. 

 9>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "C:\Dev\Cosmos-master\Build\VSIP\Cosmos.TestRunner.TestController.dll", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. [C:\Dev\Cosmos-master\source\Cosmos.IL2CPU\Cosmos.IL2CPU.csproj]

 1>Project "C:\Dev\Cosmos-master\source\Build.sln" (1) is building "C:\Dev\Cosmos-master\source\Cosmos.VS.Package\Cosmos.VS.Package.csproj" (18) on node 4 (default targets).
18>ResolveAssemblyReferences:
     Primary reference "microsoft.VisualStudio.CommonIDE, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL".
18>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "microsoft.VisualStudio.CommonIDE, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\Dev\Cosmos-master\source\Cosmos.VS.Package\Cosmos.VS.Package.csproj]

   "C:\Dev\Cosmos-master\source\Build.sln" (Build target) (1) ->
   "C:\Dev\Cosmos-master\source\Cosmos.Debug.Common\Cosmos.Debug.Common.csproj" (default target) (3) ->
   (ResolveAssemblyReferences target) -> 
     C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "System.Data.SQLite, Version=1.0.99.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. [C:\Dev\Cosmos-master\source\Cosmos.Debug.Common\Cosmos.Debug.Common.csproj]

   "C:\Dev\Cosmos-master\source\Build.sln" (Build target) (1) ->
   "C:\Dev\Cosmos-master\source\Cosmos.VS.Windows\Cosmos.VS.Windows.csproj" (default target) (24) ->
   (ResolveAssemblyReferences target) -> 
     C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed. [C:\Dev\Cosmos-master\source\Cosmos.VS.Windows\Cosmos.VS.Windows.csproj]

   "C:\Dev\Cosmos-master\source\Build.sln" (Build target) (1) ->
   "C:\Dev\Cosmos-master\source\Cosmos.Build.MSBuild\Cosmos.Build.MSBuild.csproj" (default target) (4) ->
   "C:\Dev\Cosmos-master\source\Cosmos.IL2CPU\Cosmos.IL2CPU.csproj" (default target) (9) ->
   (ResolveAssemblyReferences target) -> 
     C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "C:\Dev\Cosmos-master\Build\VSIP\Cosmos.TestRunner.TestController.dll", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. [C:\Dev\Cosmos-master\source\Cosmos.IL2CPU\Cosmos.IL2CPU.csproj]

   "C:\Dev\Cosmos-master\source\Build.sln" (Build target) (1) ->
   "C:\Dev\Cosmos-master\source\Cosmos.VS.Package\Cosmos.VS.Package.csproj" (default target) (18) ->
   (ResolveAssemblyReferences target) -> 
     C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "microsoft.VisualStudio.CommonIDE, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\Dev\Cosmos-master\source\Cosmos.VS.Package\Cosmos.VS.Package.csproj]

28 Warning(s)
0 Error(s)

Time Elapsed 00:00:14.78

Copying Templates

Change Dir: C:\Dev\Cosmos-master\Build\VSIP Copy From: C:\Dev\Cosmos-master\source\Cosmos.VS.Package\obj\Debug\CosmosProject (C#).zip To: C:\Dev\Cosmos-master\Build\VSIP\CosmosProject (C#).zip Copy From: C:\Dev\Cosmos-master\source\Cosmos.VS.Package\obj\Debug\CosmosKernel (C#).zip To: C:\Dev\Cosmos-master\Build\VSIP\CosmosKernel (C#).zip Copy From: C:\Dev\Cosmos-master\source\Cosmos.VS.Package\obj\Debug\CosmosProject (F#).zip To: C:\Dev\Cosmos-master\Build\VSIP\CosmosProject (F#).zip Copy From: C:\Dev\Cosmos-master\source\Cosmos.VS.Package\obj\Debug\Cosmos.zip To: C:\Dev\Cosmos-master\Build\VSIP\Cosmos.zip Copy From: C:\Dev\Cosmos-master\source\Cosmos.VS.Package\obj\Debug\CosmosProject (VB).zip To: C:\Dev\Cosmos-master\Build\VSIP\CosmosProject (VB).zip Copy From: C:\Dev\Cosmos-master\source\Cosmos.VS.Package\obj\Debug\CosmosKernel (VB).zip To: C:\Dev\Cosmos-master\Build\VSIP\CosmosKernel (VB).zip Copy From: C:\Dev\Cosmos-master\source\XSharp.VS\Template\XSharpFileItem.zip To: C:\Dev\Cosmos-master\Build\VSIP\XSharpFileItem.zip

Creating Inno Setup Script

Creating Setup

Starting: C:\Program Files (x86)\Inno Setup 5\ISCC.exe Params: /Q "C:\Dev\Cosmos-master\Setup\Current.iss" /dBuildConfiguration=DevKit /dVsVersion=vs2015

Running Setup

Starting: schtasks.exe Params: /run /tn "CosmosSetup"

Error

Application returned exit code. (0x00000001) at Cosmos.Build.Installer.Task.Start(String aExe, String aParams, Boolean aWait, Boolean aShowWindow) in C:\Dev\Cosmos-master\source\Cosmos.Build.Installer\Task.cs:line 112 at Cosmos.Build.Builder.CosmosTask.RunSetup() in C:\Dev\Cosmos-master\source\Cosmos.Build.Builder\CosmosTask.cs:line 632 at Cosmos.Build.Builder.CosmosTask.DoRun() in C:\Dev\Cosmos-master\source\Cosmos.Build.Builder\CosmosTask.cs:line 109 at Cosmos.Build.Installer.Task.Run() in C:\Dev\Cosmos-master\source\Cosmos.Build.Installer\Task.cs:line 16 `

jp2masa commented 8 years ago

Are you using the latest devkit?

mmcc1 commented 8 years ago

Yes, I just grabbed the zip from Github a few hours ago.

jp2masa commented 8 years ago

I had a similar error today and the cause was an error in building a solution. This log doesn't seem to be complete, try searching in your log to see if you find an error inside the Compiling Cosmos section

mmcc1 commented 8 years ago

No errors in that section.

jp2masa commented 8 years ago

It's really big, are you sure there's no error? Is "Compiling Cosmos" highlighted as red?

mmcc1 commented 8 years ago

I posted the output to PasteBin:

http://pastebin.com/drQwBjYT

mmcc1 commented 8 years ago

No, 'Running Setup' highlights red, after a few seconds it spits out the error message.

jp2masa commented 8 years ago

I'm almost sure that the setup didn't get generated

mmcc1 commented 8 years ago

Ok. So what is the solution?

jp2masa commented 8 years ago

Check Setup/Output/

jp2masa commented 8 years ago

Is there any file?

mmcc1 commented 8 years ago

Just CosmosUserKit-106027-vs2015.exe

jp2masa commented 8 years ago

Run that... I don't know why it doesn't get run automatically by the Cosmos setup

mmcc1 commented 8 years ago

I have the user kit installed already as a separate download.

mmcc1 commented 8 years ago

I'm trying to build the Devkit.

jp2masa commented 8 years ago

That's the devkit

jp2masa commented 8 years ago

The name is userkit, because it's not devkit/userkit dependant

jp2masa commented 8 years ago

So setup name has always userkit...

mmcc1 commented 8 years ago

I noticed that the Devkit request admin rights, but if you are logged in as a standard user it will attempt to install in the admin account.

mmcc1 commented 8 years ago

Ok. So, that installed. What now?

cjhannah commented 8 years ago

that's it. if it installed, follow the get started guide

jp2masa commented 8 years ago

Now you have the most recent code just use it like the userkit

mmcc1 commented 8 years ago

Is there a particular .sln to play around with the underlying code?

jp2masa commented 8 years ago

it's on source/Cosmos.sln

jp2masa commented 8 years ago

then you compile it again with install-VS2015.bat

jp2masa commented 8 years ago

or to test it before compiling you can try TestRunner

mmcc1 commented 8 years ago

Cheers, that appears to be working fine. One last question, if I were seeking to upgrade X# to x64, would that be the place to start? How does IL2CPU fit in?

jp2masa commented 8 years ago

to get x64 X# wouldn't be the best way it is for 32 bit, you would need to do a copy of X# and give it other name and add x64 on Cosmos.Assembler

mmcc1 commented 8 years ago

I saw that when I had a quick look at the code, its basically a translator between C# syntax and NASM. When it comes to IL2CPU, this is just a similar approach, is it not? Only it deals with the broader C# syntax.

jp2masa commented 8 years ago

IL2CPU just converts IL to ASM using Cosmos.Assembler through X#

mmcc1 commented 8 years ago

That's a great approach, it simplifies everything. I'll play about with X# and see if I can implement a x64 version.

jp2masa commented 8 years ago

Start by implementing x64 registers in a copy of X#, with other name, and CPU instructions in Cosmos.Assembler

mmcc1 commented 8 years ago

Ok. I'll let you know how I get on.

mmcc1 commented 8 years ago

Do you have any examples of X# programs that can be compiled by XSC.exe?

jp2masa commented 8 years ago

see Cosmos.Debug.DebugStub

jp2masa commented 8 years ago

but you currently can't use X# files for many things...

czhower commented 8 years ago

XSC is used by Cosmos to build parts of the kernel. Right now mostly the debugstub but will be expanded in the future to handle asm plugs as well.

On 9/17/2016 3:30 PM, mmcc1 wrote:

Do you have any examples of X# programs that can be compiled by XSC.exe?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CosmosOS/Cosmos/issues/471#issuecomment-247801661, or mute the thread https://github.com/notifications/unsubscribe-auth/AAbEXHR6PtQEerTU7LbDMowY8bPcQfv-ks5qrD_HgaJpZM4J_pzf.

czhower commented 8 years ago

X# could be used more. But its by design that its not. We want mostly C# code, and only X# where we cannot use C#... ie Ring 0, DebugStub, etc. The more X# code, the harder it is to port to ARM etc.

mmcc1 commented 8 years ago

I've got a copy now in a separate project and it seems to be working fine. I switched XSC to GenerateToFiles to examine the output and it seems quite good. Does it have 16 bit support? I've written bootloaders before and it would be nice to at least attempt one completely in X#.

mmcc1 commented 8 years ago

Will X# cover all forms of assembly? Will it be extended to ARM and other processors, allowing IL2CPU to compile down to any architecture?

jp2masa commented 8 years ago

for arm it will probably be A#

jp2masa commented 8 years ago

x86 and x64 both start with X so I don't know what will be better to use for x64

mmcc1 commented 8 years ago

Why not create a super language that covers all forms of assembly? Just keep expanding X#.

jp2masa commented 8 years ago

I don't know better ask @mterwoord @charlesbetros or @czhower

jp2masa commented 8 years ago

Also, if you want to discuss Cosmos, join the gitter chat

lexected commented 8 years ago

Yeah, hey, guys, this is email, not IM. Everytime one of you gets involved in a conversation here we receive a generous spam of 60 one-line emails that make no sense at all.

It's no longer fun.

Please stop.

Dňa 9/17/2016 o 10:19 PM jp2masa napísal(a):

Also, if you want to discuss Cosmos, join the gitter chat

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CosmosOS/Cosmos/issues/471#issuecomment-247805125, or mute the thread https://github.com/notifications/unsubscribe-auth/AIvSfZPM_Mu-4I1kBy84weRsSOUexuAJks5qrEs6gaJpZM4J_pzf.

fanoI commented 8 years ago

As the original issue has been resolved I'll close this now.