Jump to content

Lilu Suite builder


LAbyOne
 Share

112 posts in this topic

Recommended Posts

:star_smile: :star_smile: :star_smile: Xmas Mods's :star_smile: :star_smile: :star_smile:

 

Now @ version 1.0.7

Rewritten the code in order to make a Cleaner build, now you will just find the compiled files onto your Desktop, nothing else.

 

files and little explanation on main page

 

Edited by LAbyOne
Link to comment
Share on other sites

2 hours ago, LAbyOne said:

 

Whoops

sorry a typo... fixed now

Debug and release folders are empty.


iMac:Lilu Suite shane$ ls -la

total 0

drwxr-xr-x  4 shane  staff  128 24 Dec 22:35 .

drwx------+ 5 shane  staff  160 24 Dec 22:35 ..

drwxr-xr-x  2 shane  staff   64 24 Dec 22:35 Debug

drwxr-xr-x  2 shane  staff   64 24 Dec 22:35 Release

 

Screen Shot 2018-12-24 at 10.39.41 pm.png

Edited by SavageAUS
Link to comment
Share on other sites

30 minutes ago, SavageAUS said:

Debug and release folders are empty.

 


iMac:Lilu Suite shane$ ls -la

total 0

drwxr-xr-x  4 shane  staff  128 24 Dec 22:35 .

drwx------+ 5 shane  staff  160 24 Dec 22:35 ..

drwxr-xr-x  2 shane  staff   64 24 Dec 22:35 Debug

drwxr-xr-x  2 shane  staff   64 24 Dec 22:35 Release

 

 

Screen Shot 2018-12-24 at 10.39.41 pm.png

 

Yes, thst's an issue only happening under Mojave in fact under HS it works as expected..  it is caused by VirtualSMC itself so i can't do nothing about it.

 

The reason why your folders are empty is simply because when copying the file under mojave the "package" folder is not created ( if you open the ramdisk while building you'll see all components are there...) so it fails to copy all the others kexts as well.

i also noticed that this version has lost the efi driver (don't know if its normal as direct choice of the dev or related to some code issue..)

its something to be investigated.. as i recently didn't followed much the evolution of the project..

 

 

in the mean time, i could also upload another version of the application using a different forked source for VirtualSMC (same build ofc, to notice that this version also Still build the efi driver) which will work under mojave but i prefer wait a little while to see if this issue is solved.

 

 

  • Like 1
Link to comment
Share on other sites

its not working in Mojave with Xcode 10.1

Another suggestion is to create a folder inside the app bundle in Resources to copy the binary file

osascript -e 'do shell script "cp -R ./FOLDER/* /usr/local/bin" with administrator privileges'

manual installation of binary would no longer be necessary

Link to comment
Share on other sites

18 minutes ago, chris1111 said:

its not working in Mojave with Xcode 10.1

Another suggestion is to create a folder inside the app bundle in Resources to copy the binary file

osascript -e 'do shell script "cp -R ./FOLDER/* /usr/local/bin" with administrator privileges'

manual installation of binary would no longer be necessary

Thanls @chris1111

 

That's not the issue here, he made the screenshot to show me all necessary files are where they should be,

problem is related to actual VirtualSMC under Mojave (actually only with latest commit of alcidentera, as tested with other source from another fork still works)

Link to comment
Share on other sites

15 minutes ago, LAbyOne said:

Thanls @chris1111

 

That's not the issue here, he made the screenshot to show me all necessary files are where they should be,

problem is related to actual VirtualSMC under Mojave (actually only with latest commit of alcidentera, as tested with other source from another fork still works)

Yes that's not the issue here I have just another suggestion for the binary

 

Copying ➣this file by the bundle

mtoc

mtoc.NEW

nasm

ndisasm

Edited by chris1111
Link to comment
Share on other sites

12 minutes ago, chris1111 said:

Thanks for a suggestion this branch now works in Mojave

https://github.com/slaeensh/VirtualSMC

yes i know :)

 

BUT for the best build solution as it is now evolved, its in my honest opinion, advised to modify Only the deployment targets from actual main branch and not to reverse all implementations done till now

 

Sure that ofc worls but still is an ancient :) one. 

Edited by LAbyOne
Link to comment
Share on other sites

  • 2 weeks later...
On 9/1/2018 at 9:10 PM, iCanaro said:

maybe for a developer it is obvious, but for a normal user no, to run it must be installed xcode

 

Didn't gave it much thoughts at that time... but I guess you were right pointing that out

So even if took me sometime to do it i finally added the Xcode installation verif

 

So for Lilu Suite Builder version 1.0.8 and VirtualSMC Builder 1.0.2

Updated the code in order to make this possible :)

 

598858417_ScreenShot.png.cc9a8596680ce11f85f9a83ae9e0d60e.png2005850066_ScreenShot.png.00dc7ae0bf0006d9a2b20871c23ed213.png

 

added also the automatic detection and installation of other needed tools such as Nasm+Disasm Mtoc+Mtoc.NEW

 

949250361_ScreenShot122_55_10.png.5da1d5e160694b69c0bb5ae38201425f.png708277987_ScreenShot1.png.7525036e7f122e951fe03032cfaf8a51.png

 

So now even " a normal user " :)  will get it easier to use ...

 

 

  • Like 1
Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

New builds have been updated again

 

This new release focused mostly on solving issues under new current and upcoming Mojave builds 

 

New build goes back to acidanthera source and updated Mtoc to latest release

to install it you must delete previous version by entering Terminal and typing :

sudo rm /usr/local/bin/mtoc
sudo rm /usr/local/bin/mtoc.NEW

 

Then just launch the application you need and the new version will be installed

 

Lilu Suite Builder to version 1.1.3 and VirtualSMC Builder to version 1.0.5

  •  
Edited by LAbyOne
Link to comment
Share on other sites

54 minutes ago, telepati said:

I tried VirtualSMC Builder v1.0.5 and it was created an empty folder.

 

Lilu Suite Builder also gave me an empty folder.

 

I tried sudo command

 

1792417956_ScreenShot2019-04-04at22_13_30.png.b6ed9bab943536c27ffde6e569925eb3.png

 

 

that just mean you had no previous version on your disk into /local directpry

so once launched the application it should be installed ( or application exit )

 

about the empty folders i think You run some older version by mistake

otherwise its impossible to get such result....  check again and trash older version before...

 

 

Edited by LAbyOne
Link to comment
Share on other sites

 Share

×
×
  • Create New...