-
Notifications
You must be signed in to change notification settings - Fork 577
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
ADD linkbefore and linkafter option #250
Conversation
Allowing to set compiler options directly in the Java files makes it harder to set properties for multiple platforms. Also, it's just occurred to me that we can probably already use
Should work if we update the |
This reverts commit 3a020f6.
Sorry for late reply. It's a clever way. 😃 I resubmit a commit. And should we change the property file( |
Yes, that's what the "properties" in the command line option and in the Mojo configuration are for. I wonder if we can make this the default though? We want to merge the last prefix with the library name, but only when it doesn't end with a space, and similarly for the first suffix. Are you sure your changes do that? |
Ok, I know what's your preferred way. Please check it again. |
No, that doesn't split all spaces. We can do like it was before, but consider the parts after the first "word" in the suffix as independent options, and similar for prefix. |
@saudet done |
Looking better, almost there, but with the following properties when there are no libraries to link (like with the unit tests that you can try by running
|
@saudet I know the problem. Space before link suffix in properties should be And I modified the code, ignore link before and after options if there is no lib links |
Ah, yes, good catch! That makes it a bit harder to use, but oh well. Using a backslash to escape like this also works:
Anyway, now it looks like the whole prefix gets appended to the library name in only 1 option, including the space, like this: |
No, if I test correctly. The latest commit has splitted |
You're right, I was testing on the wrong branch, sorry. Seems to work correctly, but it's stripping the options in between each library. I'm not sure it always makes sense to do that? It wouldn't hurt to leave them at least... What do you think? |
I think I got what you mean finally.
Sorry for my bad English. Is it right? |
I think that would be best, yes, but do you think that's OK? |
It would actually be like this though:
|
Yes, I prefer that way too. It keeps meaning of
|
To have chance to add more linker options. #247