What about Mac installation?
![]()
Hello,
I do not really understand this, when I look at the instructions for the Mac so I can see that it says you should download https://www.sixxs.net/archive/sixxs/aiccu/mac/aiccu-mac-i386.exe . But what, one. Exe file for Mac?
Can anyone explain what it means. Exe files to the mac, it feels like someone has put the wrong files in the wrong place.
Thanks in advance
What about Mac installation?
.exe is just an extension to indicate that it is a binary executable. Just copy it, and run it from the console, like the normal aiccu.
What about Mac installation?
![]()
You can take a look at the instructions here:
https://www.sixxs.net/wiki/Aiccu
Aiccu installs fine on the Mac. You will need to build from source.
What about Mac installation?
You don't have to build from source, as there is a pre-compiled binary on the website, that saves at least people from having to install Xcode and other such tools.
What about Mac installation?
![]()
aa, i see. Thanks alot.
I was confused with a .exe file for mac =)
What about Mac installation?
![]()
That has changed since I last looked, though the .exe extension doesn't seem right. If you have anything like CrossOver or Parallels then it is going get associated with wrong application. That said, I am not sure what the best way to distribute it would be given it is just an executable. Maybe adding to a folder along with a 'read me' and then zipping it? If you wish I could do that.
What about Mac installation?
![]()
An even better way would be a .pkg that puts all the right things in all the right places. Maybe throw in a LaunchDaemon in for good measure.
I think I could do that -- I haven't made packages before, but PackageMaker seems straightforward enough. Actually, I might just do that. =]
Also, I'm strongly in favour of dropping the .exe extension from the Mac binary, as it's confusing for users and might get picked up by Parallels as pointed out earlier. And the Debian-style init.d startup file should not be installed on `make install` since Mac OS X doesn't use those anyway.
What about Mac installation?
These are all on the todo list and are being worked on. Actually we are modifying AICCU a lot at the moment to make it fully cross-platform available.
What about Mac installation?
![]()
Ah, cool. Drop me if there's anything I can do. I couldn't code C if my life depended on it, but I *can* compile and see if the resulting binaries work.
Will the newer version check for tun/tap availability by itself, making it a simple "drop into a directory and have a LaunchDaemon start it at boot"?
What about Mac installation?
![]()
"Drop me a line", that is. I'd rather not be dropped myself, really. =]
|