-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Makefile rules build and install are mixed and confused #29
Comments
Thanks for you comment @ryukinix, I actually felt the same way! I will change it for sure. At first I was trying to include the Brain compiler with the LLVM folder for front end, but I think that I will switch it with the local path. What do you think? |
I agree, but what do you mean by local path @luizperes? |
Actually, @rafaelcn, I was thinking about something else. What do you think about |
Great, looks good. I'd place it on: |
You can make this in next release? By the way, would be really if a full changelog been wrote in the next release and so on. thanks. i'm wating for that fix to reduce the pain of my Obsessive Compulsive Disorder. |
I will certainly do it @ryukinix!! No problem! I have the same problem (that was actually bothering me for a long time too) |
taking off milestone 1.1 |
@luizperes credo |
I might put it back, @ryukinix :P |
What do you think of placing it inside |
isn't it on |
Ops, my bad. Edited the comment, can you please take a second look? |
As talked to you on chat, I will leave it on: |
That was done here |
|
Hi @ryukinix ! Thanks for the hint! I'm reopening this issue! |
Done |
This shit is not good enough xD |
libs/install.sh this file is evil. Please, build the binary without the need to modify the operating system, injecting files or whatever be. |
Well, should it ask for the user if he wants to install in a pre defined folder |
Questions on makefile build no... :( there is no way to build without modifying the system? Build is just to build, for modify we already have the install rule.... |
I think anything about that should be only related to |
Well, you got the point. I wasn't referring to it in the |
initial external scripts should die! :D (if the user wants to extend Brain using external libraries will be still possible, but all the dependencies to |
Closed due lack of activity (> year 1). |
This is very annoying. The build triggers are getting sudo permissions to modify the OS filesystem on building the brain compiler.
I think it is better move all the statements for linking/creating libraries, move binaries and other stuffs to
install
trigger and keepbuild
rule to just... build.This is really more simple and clear.
So the INSTALL process will be:
I'm really angry about that, because I'm pain with the idiomatic way to build packages on ArchLinux don't allow to modify the OS before build the package. All the files need be put a sandbox, so after compressed, the system get all the files whose will be inserted on operating system and that way we can know exactly the files installed after it. That way is very simple remove the package.
Yes, it's very bad.
The text was updated successfully, but these errors were encountered: