hmm after trying it out, at the end i get this error

[Build] install successful
[Examine] Examining packages
Traceback (most recent call last):
  File "/usr/bin/ypkg-build", line 19, in <module>
    main()
  File "/usr/lib/python2.7/site-packages/ypkg2/main.py", line 100, in main
    build_package(args.filename, outputDir)
  File "/usr/lib/python2.7/site-packages/ypkg2/main.py", line 416, in build_package
    exaResults = exa.examine_packages(ctx, gene.packages.values())
  File "/usr/lib/python2.7/site-packages/ypkg2/examine.py", line 510, in examine_packages
    ir = self.examine_package(context, package)
  File "/usr/lib/python2.7/site-packages/ypkg2/examine.py", line 461, in examine_package
    pool = multiprocessing.Pool()
  File "/usr/lib/python2.7/multiprocessing/__init__.py", line 232, in Pool
    return Pool(processes, initializer, initargs, maxtasksperchild)
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 140, in __init__
    self._setup_queues()
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 236, in _setup_queues
    self._inqueue = SimpleQueue()
  File "/usr/lib/python2.7/multiprocessing/queues.py", line 352, in __init__
    self._rlock = Lock()
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 147, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1)
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
    sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 38] Function not implemented
ERRO[21:10:07] Failed to build package                       error="exit status 1"
ERRO[21:10:10] Failed to build packages

fixed by doing

rm /dev/shm
mkdir /dev/shm
chmod 777 /dev/shm

from https://stackoverflow.com/a/26776810/5149281
...
i have builded some packages and installed them on my solus machine and its working

I'm confused, if you want to run Solus (Linux) how is it easier to use Windows to build packages for it?

    Justin actualy i use windows most of the time and because i only have one pc
    i have to reboot everytime i want to use solus, so it is easier to work from windows instead of rebooting everytime

      We don't support WSL. Anything that has been done to support Solus in WSL is unofficial and as such I would not expect anything to work the way that it does with a normal install. For anyone reading this in the future. Do not use WSL to build packages with the intention of submitting patches. All testing should be done in a Solus install, VM or native.

        DataDrake yea i know you dont support and care about wsl
        but like i said above, i have made some packages and it works on my solus machine without any problem

            AkgunFatih Just making it clear for future readers. Wouldn't want them thinking WSL support comes from us.

              You could run solus in a VM to build stuffs if you want to stay on windows.

                kyrios i know but the reason i dont use virtualbox or vmware is that its always slow and lags on me
                if Solus had a server iso i would use it on virtualbox
                but whatever i made it work on WSL, so i have not seen any custom eopkg issues

                    AkgunFatih

                    try
                    systemctl systemctl set-default multi-user.target for non GUI.
                    and you can ssh (openssh - service should be enabled) or use VM

                    to revert back
                    systemctl systemctl set-default graphical.target for GUI

                      AkgunFatih if Solus had a server iso

                      Since Solus is a desktop distribution that focuses on home computing, this is not going to happen.

                        if you want to use Vagrant it's as simple as:

                        vagrant init tarkah/solus-budgie-4
vagrant up
vagrant ssh