When is Something Built from Source
-
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
I was comparing his VB6 output (the .exe) to the .sh file. Those are both installers.
To which .sh file? The .exe is NOT an installed. The script file of XO is not an installer either. But the .sh that we made to install it, is. VB does not create installers at all, unless you are writing your own.
Dustin said that he would install from the .exe he got from VB6 - so I was riding that wave.
@DustinB3403 said in When is Something Built from Source:
Think of Visual Basic, you write the code, design the form, and then you compile it, and get an executable that you can ship out and anyone can install the application from.
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
-
@Dashrender said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
I was comparing his VB6 output (the .exe) to the .sh file. Those are both installers.
To which .sh file? The .exe is NOT an installed. The script file of XO is not an installer either. But the .sh that we made to install it, is. VB does not create installers at all, unless you are writing your own.
Dustin said that he would install from the .exe he got from VB6 - so I was riding that wave.
You need to install it somewhere, but the exe itself isn't an installer, it is the thing to be installed.
-
@Dashrender said in When is Something Built from Source:
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
Right IF you made an installer for his VB6 application, then that would be comparable to the XO install script that we made. But the VB6 exe itself is comparable to the XO scripts themselves, the part being installed.
-
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
-
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
Right IF you made an installer for his VB6 application, then that would be comparable to the XO install script that we made. But the VB6 exe itself is comparable to the XO scripts themselves, the part being installed.
Understood and agreed. See just more more order of confusion tossed on the pile.
-
@Dashrender said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
Right IF you made an installer for his VB6 application, then that would be comparable to the XO install script that we made. But the VB6 exe itself is comparable to the XO scripts themselves, the part being installed.
Understood and agreed. See just more more order of confusion tossed on the pile.
Shouldn't be. It's all about compilation or not.
-
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
-
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
Only if? What about "checking to see if something is there" correlates with compilation? That's totally unrelated.
-
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
Only if? What about "checking to see if something is there" correlates with compilation? That's totally unrelated.
Lets take any horrid windows installer. It might check to see if .Net is installed, if not it prompts you to go an download .Net and then install .Net
Once .Net is installed, you try the installation again, this time it passes all checks.
My point is, we are checking for dependencies, and then pulling in anything required automatically.
-
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
Only if? What about "checking to see if something is there" correlates with compilation? That's totally unrelated.
Lets take any horrid windows installer. It might check to see if .Net is installed, if not it prompts you to go an download .Net and then install .Net
Once .Net is installed, you try the installation again, this time it passes all checks.
My point is, we are checking for dependencies, and then pulling in anything required automatically.
Okay, but none of those pieces are in any way related to compilation.
-
And nodejs is required (because it operate the code) for XO.
-
@DustinB3403 said in When is Something Built from Source:
And nodejs is required (because it operate the code) for XO.
RIght, it is the interpreter. We've covered these bits
The point is... nothing is being compiled, ever. -
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
And nodejs is required (because it operate the code) for XO.
RIght, it is the interpreter. We've covered these bits
The point is... nothing is being compiled, ever.So let me see if this is correct. (freaking semantics...)
drafting code in Visual Basic, is the creation of source code. The application which packages the code into an EXE or MSI would be VB's compiler.
Correct?
And if it's correct, does anyone ever really compile anything (besides maybe machine language programmers?)
If the question isn't clear, ask.
-
Or are you saying, the creation of source code is compilation?
And that packing it into an EXE for example is just something nice that we do?
-
@DustinB3403 said in When is Something Built from Source:
Or are you saying, the creation of source code is compilation?
No, I'm saying the exact opposite. Compilation is taking source code and turning it into binary for the system to execute. What compilation is is one of the most basic and well known things in computing.
-
@DustinB3403 said in When is Something Built from Source:
And that packing it into an EXE for example is just something nice that we do?
You don't pack into an EXE. An EXE (executable binary file) has no source code in it. It is a binary file that the computer itself can execute. The only thing that can make an exe file is compilation.
-
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
Or are you saying, the creation of source code is compilation?
No, I'm saying the exact opposite. Compilation is taking source code and turning it into binary for the system to execute. What compilation is is one of the most basic and well known things in computing.
Ok that makes a bit more sense.
As source code is just text, until it's able to be installed.
-
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
And that packing it into an EXE for example is just something nice that we do?
You don't pack into an EXE. An EXE (executable binary file) has no source code in it.
This I remember from high school.
-
@DustinB3403 said in When is Something Built from Source:
As source code is just text, until it's able to be installed.
No, installation and compilation are totally different things. Compilation takes source and turns it into an executable. Installation takes applications and puts them on a system. There is nothing that connections compilation and installation. Unrelated concepts.
-
Just stretching my memory.
Back in highschool (programming class) we had a project where we were using VB6 to create a game. Simon Says.
We drafted all of the code in VB6 (placed our elements into the form etc). We check our source code, confirming there are no logic errors etc. And then we hit the VB6 compile button.
That compile button, took our logic, and the "physical" elements of the form, and made an installer for our application.
What is the VB6 compiler doing specifically, that you are saying is compilation? Just taking everything we told it to, and spitting out an installer?
Still confused I guess, but I do understand, a bit.
