Status: New
Owner: ----
New issue 204 by radhermit: Setting nopycompile=YES when running make
install doesn't stop the python code from being compiled
http://code.google.com/p/solfege/issues/detail?id=204
What steps will reproduce the problem?
1. Build solfege as usual
2. Run make install while specifying nopycompile=YES to skip the
compilation of the python files.
What is the expected output? What do you see instead?
The python files shouldn't be compiled when specifying nopycompile=YES, but
they are.
What version of the product are you using? On what operating system?
This problem probably exists in pretty much every version, but I've only
patched/tested it on 3.16.4, 3.18.4, and bzr head.
See the attached patch for a fix. Basically, the patch changes the ifneq
code in the main Makefile.in to match the other ifneq calls in
help/Makefile and po/Makefile.
Attachments:
solfege-nopycompile.patch 418 bytes
------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
Solfege-devel mailing list
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe", or visit
https://lists.sourceforge.net/lists/listinfo/solfege-devel
