| 
 | 
 | 
 
Home » Developing U++ » Releasing U++ » GCC.bm problems 
	
		
		
			| GCC.bm problems [message #8649] | 
			Thu, 22 March 2007 15:09   | 
		 
		
			
				
				
				
					
						  
						ebojd
						 Messages: 225 Registered: January 2007  Location: USA
						
					 | 
					Experienced Member  | 
					 | 
		 
		 
	 | 
 
	
		There continues to be problems with the GCC.bm file missing from the source distribution.  Looking at the structure of the file I surmise that it sets up various configuration *stuff*.  I have the following questions and comments: 
 
  *) how is it generated? 
  *) when is it supposed to be generated? 
  *) how does it become "stale" or out of sync? 
 
Having this break installation should be addressed IMNSHO... 
 
 EBo -- 
		
		
		
 |  
	| 
		
	 | 
 
 
 |  
	| 
		
 |  
	| 
		
 |  
	| 
		
 |  
	| 
		
 |  
	
		
		
			| Re: GCC.bm problems [message #8743 is a reply to message #8739] | 
			Wed, 28 March 2007 21:02    | 
		 
		
			
				
				
				
					
						  
						ebojd
						 Messages: 225 Registered: January 2007  Location: USA
						
					 | 
					Experienced Member  | 
					 | 
		 
		 
	 | 
 
	
		Do we have a collection of what each of the variables are to be set for each of the platforms and compiler configurations?  My comment regarding generating it as part of the compile/install phase in the Makefile is only valid for platforms which use the Makefile to do the initial build.  If you give me a list of different configurations and settings I can probably get the Makefile to build it (either that or write a u++ app which queries the OS and configuration and builds one -- which would allow it to be regenerated on the fly with the one installed GCC.bm being the system default). 
 
  EBo -- 
		
		
		[Updated on: Wed, 28 March 2007 21:03] Report message to a moderator  
 |  
	| 
		
	 | 
 
 
 |  
	| 
		
 |  
	
		
		
			| Re: GCC.bm problems [message #8760 is a reply to message #8749] | 
			Thu, 29 March 2007 14:54    | 
		 
		
			
				
				
				
					
						  
						ebojd
						 Messages: 225 Registered: January 2007  Location: USA
						
					 | 
					Experienced Member  | 
					 | 
		 
		 
	 | 
 
	
		| luzr wrote on Wed, 28 March 2007 15:46 |  
  
Well, I am simply not sure this is worth the effort. Having existing .bm, variations are minimal and usually you can have it fixed in minutes. I think it will change two or three times on each distribution max. Fixing Makefile generator to generate .bm would be take days. Fixing generated Makefiles would not solve a problem, as you would have to fix Makefile more often then to fix .bm. 
 
Mirek
  |  
  
 
OK.  My thought was that without it, it does not just "run out of the box".  Once you have anything running, then I agree that the changes are trivial.  The real problem comes for someone building u++ for the very first time, and has no clue why it is broken...  When this happens to me I first ask myself why it does not work, then I ask myself if it is worth trying to figure out what went wrong, and lastly I ask myself if the basic install fails, then what else did they get wrong.  U++ is a really great tool, and having an install break out of the box leaves the wrong impression IMHO. 
 
  EBo -- 
		
		
		
 |  
	| 
		
	 | 
 
 
 |  
	
		
		
			| Re: GCC.bm problems [message #8761 is a reply to message #8760] | 
			Thu, 29 March 2007 15:00    | 
		 
		
			
				
				
				  | 
					
						  
						mirek
						 Messages: 14271 Registered: November 2005 
						
					 | 
					Ultimate Member  | 
					 | 
		 
		 
	 | 
 
	
		| ebojd wrote on Thu, 29 March 2007 08:54 |  
 | luzr wrote on Wed, 28 March 2007 15:46 |  
  
Well, I am simply not sure this is worth the effort. Having existing .bm, variations are minimal and usually you can have it fixed in minutes. I think it will change two or three times on each distribution max. Fixing Makefile generator to generate .bm would be take days. Fixing generated Makefiles would not solve a problem, as you would have to fix Makefile more often then to fix .bm. 
 
Mirek
  |  
  
 
OK.  My thought was that without it, it does not just "run out of the box".  Once you have anything running, then I agree that the changes are trivial.  The real problem comes for someone building u++ for the very first time, and has no clue why it is broken...  When this happens to me I first ask myself why it does not work, then I ask myself if it is worth trying to figure out what went wrong, and lastly I ask myself if the basic install fails, then what else did they get wrong.  U++ is a really great tool, and having an install break out of the box leaves the wrong impression IMHO. 
 
  EBo -- 
  |  
  
 
 
Well, I think we should rather try for per-platform presence (.deb, .rpm etc.) 
 
Mirek
		
		
		
 |  
	| 
		
	 | 
 
 
 |  
	
		
		
			| Re: GCC.bm problems [message #8766 is a reply to message #8761] | 
			Thu, 29 March 2007 17:42   | 
		 
		
			
				
				
				
					
						  
						ebojd
						 Messages: 225 Registered: January 2007  Location: USA
						
					 | 
					Experienced Member  | 
					 | 
		 
		 
	 | 
 
	
		| luzr wrote on Thu, 29 March 2007 08:00 |  
  
Well, I think we should rather try for per-platform presence (.deb, .rpm etc.) 
 
Mirek
  |  
  
 
OK.  I'll keep my specific changes in the ebuild then.   
 
  Cheers, 
 
  EBo -- 
		
		
		
 |  
	| 
		
	 | 
 
 
 |   
Goto Forum:
 
 Current Time: Tue Nov 04 13:47:59 CET 2025 
 Total time taken to generate the page: 0.05920 seconds 
 |   
 |  
  |