• What are you working on? v19
    6,590 replies, posted
The absence of a comma does not change the meaning of that sentence, it merely makes it incomprehensible unless you assume the comma is implied. [editline]14th August 2011[/editline] Ie fuck commas real men use no punctuation at all
[QUOTE=esalaka;31724779]The absence of a comma does not change the meaning of that sentence, it merely makes it incomprehensible unless you assume the comma is implied. [editline]14th August 2011[/editline] Ie fuck commas real men use no punctuation at all[/QUOTE] The lack of a comma fucked over what I thought it meant, I thought it meant that no version of VirtualBox fully supported EFI.
I always thought there's only one VirtualBox but I guess you could think of each version as a separate one :v:
I think you're just nit picking
[QUOTE=CarlBooth;31724513]Yeah, it runs natively on VirtualBox Only a [url=http://pastebin.com/C3YUD8b9]slight config change[/url] is needed in the machine XML file, no changes to OS X required. I even used a Retail DVD from my Macbook.[/QUOTE] Why have I never read about this config change in any of the guides I read? Suddenly everything works perfectly fine.
[QUOTE=Overv;31725009]Why have I never read about this config change in any of the guides I read? Suddenly everything works perfectly fine.[/QUOTE] youre supposed to be a wwizard if you read them prob'ly [editline]14th August 2011[/editline] Okay, fuck this, I'll just get back to proper grammar. I'm not even proving a point.
[QUOTE=Overv;31725009]Why have I never read about this config change in any of the guides I read? Suddenly everything works perfectly fine.[/QUOTE] Apple allow OS X Server to be virtualised, it will install without any changes. I think that line just adds an emulation for a check OS X Client makes to see if it is licensed to run or not.
[QUOTE=CarlBooth;31725035]Apple allow OS X Server to be virtualised, it will install without any changes. I think that line just adds an emulation for a check OS X Client makes to see if it is licensed to run or not.[/QUOTE] If I'm not mistaken that key just allows DSMOS to run, DSMOS stands for "Don't Steal Mac OS". Basically it stops OSX running on non Mac hardware.
[QUOTE=wingless;31725088]If I'm not mistaken that key just allows DSMOS to run, DSMOS stands for "Don't Steal Mac OS". Basically it stops OSX running on non Mac hardware.[/QUOTE] I wonder what SmcDeviceKey means. What's the Smc stand for?
[QUOTE=esalaka;31725112]I wonder what SmcDeviceKey means. What's the Smc stand for?[/QUOTE] System Management Controller.
[QUOTE=wingless;31725128]System Management Controller.[/QUOTE] So is it a separate chip on Macs or something? [editline]14th August 2011[/editline] Because sounds like it's the piece of hardware used to restrict usage to only Apple-produced platforms
[QUOTE=esalaka;31725156]So is it a separate chip on Macs or something? [editline]14th August 2011[/editline] Because sounds like it's the piece of hardware used to restrict usage to only Apple-produced platforms[/QUOTE] Yeah but it controls all the fans and all sorts of shit. It's like a little ROM.
Sorry if I'm a little late, but the OpenGL context creation tutorial works fine on Code::Blocks on windows. You just need to create a new OpenGL project, for some reason creating an empty project and linking liopengl32.a gives linker errors.
-snip-
[QUOTE=Robbis_1;31722908]What is that? A cube of cubes? Or is it just lots of cubes on the same position?[/QUOTE] They are actually GL_POINTS, 2d dots rendered in 3d space. It gives some interesting pictures and is fairly fast at rendering.
Overv, you might want to remind that these apt-get commands are for Debian and Debian-based distributions only. Fedora users will have to use yum..., Arch users will have to use pacman (although the development libraries are installed automatically with xorg and mesa/libgl), and Gentoo users can go fuck themselves. [b]edit[/b]: Also, "gl/glext.h" and "gl/glxext.h" should be <GL/glext.h> and <GL/glxext.h> respectively, if you're installing them in /usr/include (and you shouldn't).
[QUOTE=q3k;31725747]Overv, you might want to remind that these apt-get commands are for Debian and Debian-based distributions only. Fedora users will have to use yum..., Arch users will have to use pacman (although the development libraries are installed automatically with xorg and mesa/libgl), and Gentoo users can go fuck themselves. [b]edit[/b]: Also, "gl/glext.h" and "gl/glxext.h" should be <GL/glext.h> and <GL/glxext.h> respectively, if you're installing them in /usr/include (and you shouldn't).[/QUOTE] And that's why I'm not using angle brackets. I assume Linux developers know that, it's part of the prior C++ experience.
[QUOTE=Overv;31725807]And that's why I'm not using angle brackets. I assume Linux developers know that, it's part of the prior C++ experience.[/QUOTE] Yeah, I guess you're right. Also, your example code works well for me. Are you sure you want people to use Code::Blocks instead of their favourite text editor and a Makefile (either created manually, it's not that hard, using CMake, or gods forbid using autotools)?
[QUOTE=q3k;31725747]Overv, you might want to remind that these apt-get commands are for Debian and Debian-based distributions only. Fedora users will have to use yum..., Arch users will have to use pacman (although the development libraries are installed automatically with xorg and mesa/libgl), and Gentoo users can go fuck themselves. [b]edit[/b]: Also, "gl/glext.h" and "gl/glxext.h" should be <GL/glext.h> and <GL/glxext.h> respectively, if you're installing them in /usr/include (and you shouldn't).[/QUOTE] I don't know much about programming on Linux, so I'm wondering why you shouldn't install them there?
Arch automatically installs them there if you install from the repositiories. I too wonder why you shouldn't install them in /usr/include as i have them located there?
[QUOTE=q3k;31725859]Yeah, I guess you're right. Also, your example code works well for me. Are you sure you want people to use Code::Blocks instead of their favourite text editor and a Makefile (either created manually, it's not that hard, using CMake, or gods forbid using autotools)?[/QUOTE] I don't recall using Code::Blocks anywhere? I specified the arguments to compile your code with GCC, so you are free to use anything you want to edit and build your project.
[QUOTE=thf;31725892]I don't know much about programming on Linux, so I'm wondering why you shouldn't install them there?[/QUOTE] Because it's a system path, and your package manager might complain, some apps depending on an older versions of these files might break... You should either install there headers in /usr/local/include, or just keep them local to your current project. The same goes for all software that isn't managed by your package manager, it should always go to /usr/local instead of /usr, or updates might collide with your custom files.
[QUOTE=Naelstrom;31725908]Arch automatically installs them there if you install from the repositiories. I too wonder why you shouldn't install them in /usr/include as i have them located there?[/QUOTE] You shouldn't count on them being there, I s'pose.
[QUOTE=Overv;31725917]I don't recall using Code::Blocks anywhere? I specified the arguments to compile your code with GCC, so you are free to use anything you want to edit and build your project.[/QUOTE] In your "full source code" file: [cpp]/// Describe Code::Blocks setup and how to compile with g++[/cpp] [editline]14th August 2011[/editline] [QUOTE=esalaka;31725928]You shouldn't count on them being there, I s'pose.[/QUOTE] They might not be the most recent version available. Well, maybe not on Arch but on other distributions.
[QUOTE=q3k;31725935]In your "full source code" file: [cpp]/// Describe Code::Blocks setup and how to compile with g++[/cpp][/QUOTE] That shouldn't be in the source code on the site, sorry :v:.
Development is slow so have a video of me dicking around in 1-1! [media]http://www.youtube.com/watch?v=WtcGiZelPfk[/media] Outsmarting enemies is fun.
[QUOTE=Maurice;31726031]Development is slow so have a video of me dicking around in 1-1! [media]http://www.youtube.com/watch?v=WtcGiZelPfk[/media] Outsmarting enemies is fun.[/QUOTE] Whenever you release it, I'll send it to tons of gaming websites and make you famous.
[QUOTE=Maurice;31726031]Development is slow so have a video of me dicking around in 1-1! [media]http://www.youtube.com/watch?v=WtcGiZelPfk[/media] Outsmarting enemies is fun.[/QUOTE] Cool. (What happened to your avatar :ohdear:)
So I have this 2D rendering library thing and it can do stuff with OpenGL. I decided to try and add 3D functionality to it. It was surprisingly easy. [img]http://dl.dropbox.com/u/35032740/ZScreen/Oooh_3D%21-2011-08-14_17.06.55.png[/img] The cube rotates. This is the code used: [csharp]using FireflyGL; namespace Oooh3D { static class Program { static Cube cube; static void Main() { Firefly.OnUpdate += delegate { cube.Yaw = Firefly.ElapsedMilliseconds / 1000F; cube.Roll = Firefly.ElapsedMilliseconds / 1000F; }; Firefly.Initialize(800, 500, "Oooh 3D!", (x, y) => OnLoad()); } static void OnLoad() { cube = new Cube(); cube.FrontTopLeft.G = 0; cube.FrontTopLeft.B = 0; cube.FrontTopRight.R = 0; cube.FrontTopRight.B = 0; cube.FrontBottomRight.R = 0; cube.FrontBottomRight.G = 0; cube.FrontBottomLeft.B = 0; cube.BackTopRight.B = 0; cube.BackTopLeft.R = 0; cube.BackTopLeft.G = 0; cube.BackBottomRight.B = 0; cube.BackBottomRight.G = 0; cube.BackBottomLeft.B = 0; cube.BackBottomLeft.R = 0; cube.Z -= 5F; var test = new Label("Hello\nThis is text rendered on the scene\nusing orthogonal projection over the \ncube that's rendered in 3D", new System.Drawing.Font("Impact", 18), System.Drawing.Brushes.Green) { X = 400, Y = 300 }; } } } [/csharp]
[QUOTE=esalaka;31726194](What happened to your avatar :ohdear:)[/QUOTE] It became 20% cooler.
Sorry, you need to Log In to post a reply to this thread.